call_tool · MCP Test MCP: Risk & Policy

WHAT IT DOES

What call_tool does on MCP Test MCP

AI agents invoke call_tool to trigger actions in MCP Test MCP. 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.

WHY IT NEEDS A POLICY

Why call_tool needs a policy

The tool name 'call_tool' strongly implies it executes/invokes tools, potentially on external MCP servers. Given the server's purpose of testing other MCP servers by executing calls, this tool likely dispatches arbitrary tool calls to connected servers, which could trigger any category of action (including destructive or financial operations) depending on what tool is called. This makes it critical severity.

From the tool's definition Tool name 'call_tool' on a server described as a 'testing harness that enables AI assistants to thoroughly test other MCP servers by...executing test calls'.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

call_tool Rate-limited

call_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "call_tool": {
      "limits": [
        {
          "counter": "call_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Test MCP, so you can run agents against it safely.

FAQ

Questions about call_tool

What does the call_tool tool do? +

call_tool. It is categorised as a Execute tool in the MCP Test MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on call_tool? +

Register the MCP Test 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 Test MCP. Nothing to install.

What risk level is call_tool? +

call_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit call_tool? +

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.

How do I block call_tool completely? +

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.

What MCP server provides call_tool? +

call_tool is provided by the MCP Test MCP server (rdwj/mcp-test-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.