Returns the diff of current changes in the workspace.
AI agents call vc_diff to retrieve information from Agent-VC MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only reads and returns information about current workspace changes (a diff). It has no side effects and does not modify, execute, or delete anything.
From the tool's definition Returns the diff of current changes in the workspace
Attacks that exploit this kind of access
Returns the diff of current changes in the workspace. It is categorised as a Read tool in the Agent-VC MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Agent-VC MCP Server MCP server in PolicyLayer and add a rule for vc_diff: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Agent-VC MCP Server. Nothing to install.
vc_diff is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the vc_diff rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for vc_diff. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
vc_diff is provided by the Agent-VC MCP Server MCP server (manbothq/agent-vc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →