terminal_cd
AI agents invoke terminal_cd to trigger actions in Global MCP Manager. 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.
The tool name 'terminal_cd' strongly suggests a change-directory operation in a terminal context. While changing directories is generally low-risk on its own, within this server's context of executing terminal commands across local, SSH, and remote environments, navigating directories could be a precursor to or part of broader execution workflows. The description is empty, lowering confidence.
From the tool's definition Tool name 'terminal_cd' on a server described as enabling 'executing terminal commands' across local, SSH, and GitHub contexts
Attacks that exploit this kind of access
terminal_cd. It is categorised as a Execute tool in the Global MCP Manager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Global MCP Manager MCP server in PolicyLayer and add a rule for terminal_cd: 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_cd 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_cd 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_cd. 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_cd 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 →