Get the status of the repository
AI agents call vcs_status to retrieve information from Node Dev MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves version control status (likely git status output showing uncommitted changes, branch information, etc.). It is a read-only operation with no side effects, no code execution, and no data modification. The low severity reflects minimal blast radius even if misused by an AI agent.
From the tool's definition Tool name 'vcs_status' and description 'Get the status of the repository' indicate a query operation that retrieves repository state information without modifying or executing anything.
Attacks that exploit this kind of access
Get the status of the repository. It is categorised as a Read tool in the Node Dev MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Node Dev MCP Server MCP server in PolicyLayer and add a rule for vcs_status: 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 Node Dev MCP Server. Nothing to install.
vcs_status 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 vcs_status 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 vcs_status. 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.
vcs_status is provided by the Node Dev MCP Server MCP server (liamcarver/node-dev-mcp-server). 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 →