AI agents invoke execute_script to trigger actions in Mcp Ssh. 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 allows execution of scripts on remote systems via SSH with effects determined entirely by the script arguments provided by an AI agent. This is a classic Execute category risk—external code/operations triggered by user-controlled input.
From the tool's definition Tool named 'execute_script' on an SSH MCP server for 'command execution' and 'remote Linux/Unix server management'. The server description explicitly states it enables 'command execution' and the tool name indicates arbitrary script execution capability.
Attacks that exploit this kind of access
execute_script. It is categorised as a Execute tool in the Mcp Ssh MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Mcp Ssh MCP server in PolicyLayer and add a rule for execute_script: 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 Ssh. Nothing to install.
execute_script 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 execute_script 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 execute_script. 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.
execute_script is provided by the Mcp Ssh MCP server (zhouxiangjing/mcp-ssh). 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 →