approve_request
Approve a pending approval request.
This record as markdown: /tools/bhayanak-ssh-mcp-server/approve-request.md
What approve_request does on SSH MCP Server
AI agents invoke approve_request to trigger actions in SSH 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.
Why approve_request is rated High
Approving a pending request triggers an external operation or workflow that may have cascading effects (e.g., granting SSH access, issuing certificates, executing commands on remote servers). The action is not purely a read, and while it could be reversible in some contexts, approving access or operations on remote Linux servers carries a high blast radius if misused by an AI agent.
From the tool's definition Approve a pending approval request
Attacks that exploit this kind of access
The rule that runs approve_request safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SSH MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For approve_request, this is the rule to start with:
approve_request stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SSH MCP Server, apply this rule, and every approve_request call is checked against it from then on.
Questions about approve_request
Approve a pending approval request. It is categorised as a Execute tool in the SSH MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the SSH MCP Server MCP server in PolicyLayer and add a rule for approve_request: 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 SSH MCP Server. Nothing to install.
approve_request 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 approve_request 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 approve_request. 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.
approve_request is provided by the SSH MCP Server MCP server (bhayanak/ssh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SSH MCP Server, and thousands of servers like it.
Across the catalogue