VS Code CopilotIDE

Cerbos (Access Control) MCP Server

Bring Authorization
to VS Code Copilot

Name: Cerbos (Access Control) MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

Learn how to connect Cerbos (Access Control) to VS Code Copilot and start using 19 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Add PolicyAdd SchemaAuthzen EvaluationAuthzen EvaluationsCheck ResourcesDelete PolicyDisable PolicyEnable PolicyGet Authzen ConfigGet HealthGet MetricsGet PolicyGet SchemaGet Server InfoList Audit LogsList PoliciesList SchemasPlan ResourcesUpdate Policy

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Cerbos (Access Control) MCP Server?

Connect your Cerbos instance to any AI agent to streamline authorization management and policy auditing through natural language.

What you can do

Permission Checks — Use check_resources to evaluate if a principal (user) has the rights to perform specific actions on resources.
Query Planning — Generate AST query plans with plan_resources to filter database results based on complex authorization logic.
Policy Management — List, retrieve, add, or delete policies (RBAC/ABAC) using the Admin API tools like list_policies and add_policy.
Schema & Auditing — Inspect resource schemas and review access logs with list_auditLogs to ensure compliance.
Health & Metrics — Monitor your PDP (Policy Decision Point) status with get_health and get_metrics directly from the chat.

How it works

Subscribe to this server
Enter your Cerbos PDP URL and Admin credentials (if required for policy management)
Start auditing and managing your access control logic from Claude, Cursor, or any MCP client

Who is this for?

Security Engineers — quickly audit existing policies and verify permission logic without manual API calls
Backend Developers — test authorization scenarios and generate database filter plans during development
Compliance Officers — retrieve audit logs and policy definitions to ensure organizational security standards

Built-in capabilities (19)

add_policy

Add a new policy

add_schema

Add or update a schema

authzen_evaluation

Perform a single AuthZEN access evaluation

authzen_evaluations

Perform batch AuthZEN access evaluations

check_resources

Check permissions for a set of resources

delete_policy

Delete a policy by ID

disable_policy

Disable a policy

enable_policy

Enable a policy

get_authzen_config

Get AuthZEN configuration metadata

get_health

Get Cerbos health status

get_metrics

Get Prometheus metrics from Cerbos

get_policy

Get a specific policy by ID

get_schema

Get a specific schema by ID

get_server_info

Get Cerbos server version and build information

list_audit_logs

List audit logs

list_policies

List all policies

list_schemas

List all schemas

plan_resources

Produce a query plan (AST) for filtering resources

update_policy

Update an existing policy

Why VS Code Copilot?

GitHub Copilot Agent mode brings Cerbos (Access Control) data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 19 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

—
VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor
—
Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access
—
Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop
—
GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Cerbos (Access Control) in VS Code Copilot

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Cerbos (Access Control) and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Cerbos (Access Control) to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for VS Code Copilot →

Enterprise Security

Why teams choose Vinkius for Cerbos (Access Control) in VS Code Copilot

The Cerbos (Access Control) MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 19 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Cerbos (Access Control) details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Cerbos (Access Control) for VS Code Copilot

Every tool call from VS Code Copilot to the Cerbos (Access Control) MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I test if a specific user has access to a resource without writing code?

Yes. You can ask the agent to use the check_resources tool by providing the principal (user) details and the resource you want to check. The agent will return the allowed or denied status based on your Cerbos policies.

How do I view all the authorization policies currently loaded in my Cerbos server?

Simply ask the agent to 'list all policies'. It will invoke the list_policies tool (requires Admin credentials) and display the IDs of all active policies in your environment.

Can the AI help me generate filters for my database based on permissions?

Yes, by using the plan_resources tool. The agent will generate a query plan (AST) that describes the conditions under which a user is allowed to access resources, which you can then apply to your database queries.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.