High-risk tools in MCP Stdio Wrapper
3 of the 15 tools in MCP Stdio Wrapper are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
stdio_mcp_call_toolExecuteLaunch a target stdio MCP server and call one of its tools. Best for stateless single calls; if the target preserves in-memory state or returns deferred handles, prefer stdio_mc...
-
stdio_mcp_open_sessionExecuteLaunch a target stdio MCP server and keep it alive for multiple MCP operations. Use this when follow-up calls need the same target process, deferred handles, or expensive startu...
-
stdio_mcp_session_call_toolExecuteCall a target MCP tool through a previously opened session.
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.