Run a shell command inside the user's own deployed app container and return the result. Uses a fixed 360-second backend timeout. Keep input at or below 10,000 characters and about 350 lines. This is limited to the caller's app pod only.
AI agents invoke exec_app_terminal to trigger actions in PlugLayer 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.
This tool allows execution of arbitrary shell commands within a container environment. While scoped to 'the caller's app pod only' (reducing blast radius), arbitrary command execution can still enable: credential theft, data exfiltration, lateral movement within the container, deployment of malware, or disruption of services.
From the tool's definition Tool explicitly states it 'Run[s] a shell command inside the user's own deployed app container and return the result.' The ability to execute arbitrary shell commands is the definition of Execute category.
Attacks that exploit this kind of access
Run a shell command inside the user's own deployed app container and return the result. Uses a fixed 360-second backend timeout. Keep input at or below 10,000 characters and about 350 lines. This is limited to the caller's app pod only. It is categorised as a Execute tool in the PlugLayer MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PlugLayer MCP Server MCP server in PolicyLayer and add a rule for exec_app_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 PlugLayer MCP Server. Nothing to install.
exec_app_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 exec_app_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 exec_app_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.
exec_app_terminal is provided by the PlugLayer MCP Server MCP server (pluglayer/mcp). 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 →