AI agents invoke call_tool to trigger actions in Mcp Proxy. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary operations on backend MCP servers. Since it can invoke any tool available on those servers without apparent restrictions, it has the blast radius of an Execute category tool — it can trigger code execution, shell commands, data modifications, or destructive operations depending on the backend tools available.
From the tool's definition Tool description states 'Execute a tool on a proxied MCP server.' The word 'Execute' directly indicates runtime code execution capabilities.
Attacks that exploit this kind of access
Execute a tool on a proxied MCP server. It is categorised as a Execute tool in the Mcp Proxy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Proxy MCP server in PolicyLayer and add a rule for call_tool: 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 Mcp Proxy. Nothing to install.
call_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_tool 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 call_tool. 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.
call_tool is provided by the Mcp Proxy MCP server (shengxiao20/mcp-proxy-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 →