stdio_mcp_session_call_tool · MCP Stdio Wrapper MCP

WHAT IT DOES

What stdio_mcp_session_call_tool does on MCP Stdio Wrapper

AI agents invoke stdio_mcp_session_call_tool to trigger actions in MCP Stdio Wrapper. 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 stdio_mcp_session_call_tool needs a policy

This tool executes arbitrary tools on a target MCP server through an established session. Since it can invoke any tool on any connected MCP server, its blast radius is unbounded — it could trigger Read, Write, Execute, Destructive, or Financial operations depending on what tool is called.

From the tool's definition Call a target MCP tool through a previously opened session

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

stdio_mcp_session_call_tool Rate-limited

stdio_mcp_session_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": {
    "stdio_mcp_session_call_tool": {
      "limits": [
        {
          "counter": "stdio_mcp_session_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 Stdio Wrapper, so you can run agents against it safely.

FAQ

Questions about stdio_mcp_session_call_tool

What does the stdio_mcp_session_call_tool tool do? +

Call a target MCP tool through a previously opened session. It is categorised as a Execute tool in the MCP Stdio Wrapper MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stdio_mcp_session_call_tool? +

Register the MCP Stdio Wrapper MCP server in PolicyLayer and add a rule for stdio_mcp_session_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 Stdio Wrapper. Nothing to install.

What risk level is stdio_mcp_session_call_tool? +

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

Can I rate-limit stdio_mcp_session_call_tool? +

Yes. Add a rate_limit block to the stdio_mcp_session_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 stdio_mcp_session_call_tool completely? +

Set action: deny in the PolicyLayer policy for stdio_mcp_session_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 stdio_mcp_session_call_tool? +

stdio_mcp_session_call_tool is provided by the MCP Stdio Wrapper MCP server (joshuagreeff/mcp-stdio-wrapper). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.