request_approval
Request approval for a privileged (Tier 2) operation.
This record as markdown: /tools/bhayanak-ssh-mcp-server/request-approval.md
What request_approval does on SSH MCP Server
AI agents invoke request_approval 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 request_approval is rated High
This tool initiates a privileged operation approval workflow, triggering an external process that can lead to execution of elevated/privileged operations on remote Linux servers. While the tool itself requests approval rather than directly executing, it is the gateway to high-impact privileged actions.
From the tool's definition Request approval for a privileged (Tier 2) operation
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs request_approval 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 request_approval, this is the rule to start with:
request_approval 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 request_approval call is checked against it from then on.
Questions about request_approval
Request approval for a privileged (Tier 2) operation. 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 request_approval: 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.
request_approval 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 request_approval 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 request_approval. 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.
request_approval 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