Run terminal commands and return the output.
AI agents invoke terminal to trigger actions in Terminal MCP Server. 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.
Shell command execution is a quintessential Execute category risk. An AI agent given access to this tool can run any command the underlying process permits—including data exfiltration, system reconnaissance, lateral movement, malware deployment, or destructive operations. While the server provides 'timeout protection,' this does not constrain what commands can be executed, only their duration.
From the tool's definition Tool description states 'Run terminal commands and return the output.' Combined with server description 'Enables execution of shell commands through a terminal tool,' this tool directly executes arbitrary shell commands.
Attacks that exploit this kind of access
Run terminal commands and return the output. It is categorised as a Execute tool in the Terminal MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Terminal MCP Server MCP server in PolicyLayer and add a rule for terminal: 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 Terminal MCP Server. Nothing to install.
terminal 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 terminal 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 terminal. 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.
terminal is provided by the Terminal MCP Server MCP server (yongpengfu/mcp-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 →