terminal_remove
AI agents call terminal_remove to permanently remove resources in Global MCP Manager — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Despite the empty description, the tool name 'terminal_remove' combined with the server's documented file management capabilities and multi-environment scope (local, SSH, GitHub) indicates this tool deletes files or directories. Deletion is irreversible and cannot be undone, making it Destructive rather than Write.
From the tool's definition Tool name 'terminal_remove' in a terminal command execution context; server description explicitly states 'file operations' and 'multi-environment command execution' across local, SSH, and GitHub contexts. The 'remove' operation is irreversible deletion.
Attacks that exploit this kind of access
terminal_remove. It is categorised as a Destructive tool in the Global MCP Manager MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Global MCP Manager MCP server in PolicyLayer and add a rule for terminal_remove: 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 Global MCP Manager. Nothing to install.
terminal_remove is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the terminal_remove 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_remove. 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_remove is provided by the Global MCP Manager MCP server (mamprimauto/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 →