securityidentitytrustmcpagent-control
Action-control layer for AI agents providing trust, identity, attestation, and risk-based decision mediation.
Quick Install
Automated & IDE SetupCopy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.
We couldn’t automatically confirm this listing starts correctly
We ran the install command below but it didn't respond within our test window — this can mean a slow first-time install rather than a real problem.
uvx agentveil-mcp-proxyNo response to initialize.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked 1mo ago.
Manual Client & Custom JSON ConfigExpand JSON ▾
Client Config & Setup
Choose your client or environment
Target File:
💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.
Overview
Use cases
Control and approve risky AI agent actions before execution
Redirect agent actions to safer controlled MCP routes
Record bounded local evidence of agent decisions and actions
Detect and handle identity, sybil attacks, and disputes
Anchor audit data on IPFS for verifiable evidence
Key features
Mediates native and routed MCP actions with allow, approval, redirect, or hard-block decisions
Supports W3C Decentralized Identifiers (DIDs) for identity
EigenTrust reputation system integration
Attestation and dispute management
Sybil detection mechanisms
Local bounded evidence recording with request IDs and hashes
Capabilities & Tool Schemas
Inspect callable tools, capabilities, and parameters exposed to AI agents by Avp Sdk.
Extracted Tool Capabilities
Mediates native and routed MCP actions with allow, approval, redirect, or hard-block decisions
Supports W3C Decentralized Identifiers (DIDs) for identity
EigenTrust reputation system integration
Attestation and dispute management
Sybil detection mechanisms
Local bounded evidence recording with request IDs and hashes
Documentation Overview
AgentVeil
The risk isn't what AI says. It's what AI does.
AgentVeil is an independent action-control layer for AI agents and MCP tools. It works alongside agent runtimes such as Cursor, Claude Code, Codex, Gemini CLI, and Hermes CLI: attempt, decision, controlled path when available, local proof.
Quick Start · The Loop · Connectors · Evidence · Scope · Design Basis · Docs
Packages: agentveil-mcp-proxy · agentveil | Website: agentveil.dev | Package source: packages/agentveil-mcp-proxy/
Agent action boundary: AI runtimes execute agents. AgentVeil mediates configured action paths around them. When a native or risky action hits the boundary, AgentVeil decides allow, approval required, redirect guidance toward a controlled path, or hard-block. Routed MCP calls follow the same decision model and record bounded local evidence.
AgentVeil is not machine-wide control. Actions outside configured AgentVeil boundaries are not classified or logged.
Visual overview: request → AgentVeil boundary → redirect / approval / hard-block → local proof.
Data handling: AgentVeil is designed to keep raw MCP arguments local by default and to record bounded metadata and hashes for evidence. See Data Handling.
The AgentVeil Loop
AgentVeil is one product loop, not a pile of separate components:
| Step | What happens |
|---|---|
| Attempt | Agent tries a native mutation or routed MCP action in a configured project |
| Decision | AgentVeil returns allow, approval required, redirect, or hard-block |
| Controlled path | When one is available, redirect guidance tells the agent to retry through the managed MCP route |
| Proof | Bounded local evidence records the decision; inspect it with events show --last |
Approval fixes actions that need human review. Redirect tells the agent to retry through the controlled MCP route when one is available. Hard-block means approval will not help for that action. Local proof is available now through the CLI—not a future dashboard page.
What AgentVeil Adds
AgentVeil is not an AI agent and does not replace an agent runtime. It adds a control layer around actions that are configured to pass through AgentVeil.
| Layer | Agent runtime / framework | AgentVeil adds |
|---|---|---|
| Execution | Runs the agent and exposes tools | Mediates configured action paths before execution |
| Approval | May prompt per tool call, depending on runtime | Adds policy-aware approval for routed writes and mutations |
| Risk classification | Runtime-specific, if present | Shared read / write / destructive / unknown classification |
| Sandbox boundary | Runtime-specific | Project or downstream sandbox limits for routed actions |
| Evidence | Usually chat or runtime logs | Bounded local records with request ids, decisions, and hashes |
| Cross-runtime consistency | Per runtime | Same core control semantics where actions are routed through AgentVeil |
Quick Start
Use AgentVeil with a supported project connector, or run the Core MCP Proxy directly.
Cursor project connector
Choose the project folder you want to protect, then reopen / reload Cursor for that project.
After setup, in the configured project:
- supported native risky agent actions can be blocked before execution;
- the agent receives redirect guidance toward the AgentVeil MCP route;
- routed MCP writes can require approval;
- AgentVeil records bounded local evidence for decisions and outcomes.
Some Cursor versions may require enabling the managed agentveil-mcp-proxy MCP server once in Tools & MCPs after reload.
Claude Code project connector
Choose the project folder you want to protect, then reopen / reload Claude Code for that project.
After setup, in the configured project:
- supported native Claude Code mutation tools are checked by a project-local hook;
- risky native mutations are blocked with redirect guidance toward the controlled MCP route;
- AgentVeil MCP writes go through the proxy approval path;
- bounded evidence is written locally.
Codex project connector
Choose the project folder you want to protect, then open / restart Codex for
that project. Codex asks you to trust the AgentVeil project hook once; until
the hook fires and evidence is observed, setup status --client codex remains
advisory, not protected.
After setup and hook trust, in the configured project:
- supported native Codex mutation tools are checked by a project-local hook;
- risky native mutations are blocked with redirect guidance toward the controlled MCP route;
- AgentVeil MCP writes go through the proxy approval path;
- bounded evidence is written locally.
Gemini CLI project connector
Choose the project folder you want to protect, then open / restart Gemini CLI for that project. Gemini CLI asks you to trust the project folder before it loads local settings, hooks, and MCP servers.
After setup and folder trust, in the configured project:
- supported native Gemini CLI mutation tools are checked by a project-local hook;
- risky native mutations are blocked with redirect guidance toward the controlled MCP route;
- AgentVeil MCP writes go through the proxy approval path;
- bounded evidence is written locally.
Hermes CLI controlled MCP profile
Hermes CLI is launched through AgentVeil rather than installed as a persistent project hook:
The launcher configures a project-local Hermes home, routes Hermes to the AgentVeil MCP tools, and keeps local proof/evidence in the selected project.
In this profile:
- Hermes project work is routed through the AgentVeil MCP route;
- routed reads, writes, approval, sandbox boundaries, redirect guidance, and local proof use the shared AgentVeil control layer;
- native Hermes tools are limited by profile settings, but AgentVeil does not claim host-wide control of Hermes or the machine.
Core MCP Proxy path
For lower-level MCP routing without an IDE connector:
This starts the core route: MCP tool calls explicitly pointed at agentveil-mcp-proxy.
Verify your setup works
After installing a project connector, walk the current shipped path in that project:
- Ask the agent to read project context. Routed reads such as
list_workspace,read_file,get_file_info, andinstruction_surface_statusshould allow. - Ask the agent to create or edit a file, for example:
The configured connector should stop the native mutation with redirect guidance; the agent should then use the controlled MCP route, where risky writes require approval. 3. Open the approval page when prompted and review the bounded proof details. 4. Inspect local proof from the CLI:
The default human output should include lines like
decision=approval_required and tool=write_file without dumping raw JSON.
Use --json when you need structured fields.
Connectors Available Today
AgentVeil is built around action-control boundaries. Cursor, Claude Code, Codex, and Gemini CLI are supported project hook connectors. Hermes CLI is available as a controlled MCP launch profile. The Core MCP Proxy is runtime-agnostic for MCP clients that are explicitly configured to call it.
Related MCP Servers
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
GitHub stars
15
Stargazers on the source repository.
Last commit
16d ago
Most recent push to the default branch.
Install check
Inconclusive
Didn't respond in our test window — often a slow first install.
Directory activity
2 views
Config copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how this listing worked for you.
Frequently Asked Questions about Avp Sdk
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/creatorrmode-lead-avp-sdk)HTML Embed
<a href="https://allmcps.com/mcp/creatorrmode-lead-avp-sdk"><img src="https://allmcps.com/api/badge/creatorrmode-lead-avp-sdk?style=directory" alt="Avp Sdk on AllMCPs" /></a>