Reject a stored plan so it cannot be executed
AI agents call ssh_reject_plan as a supporting operation in SSH Remote MCP Server workflows.
This tool prevents execution of a plan rather than creating, modifying, deleting, or executing anything itself. It is a control/governance action that blocks a plan from running, which doesn't fit neatly into Read, Write, Execute, Destructive, Financial categories. It's a meta-operation that cancels a pending action, reducing risk rather than increasing it.
From the tool's definition 'Reject a stored plan so it cannot be executed'
Documented attack patterns abuse exactly the kind of access ssh_reject_plan gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and SSH Remote MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ssh_reject_plan:
{
"version": "1",
"default": "deny",
"tools": {
"ssh_reject_plan": {
"limits": [
{
"counter": "ssh_reject_plan_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} ssh_reject_plan gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Reject a stored plan so it cannot be executed. It is categorised as a Other tool in the SSH Remote MCP Server MCP Server, which means it performs auxiliary operations.
Register the SSH Remote MCP Server MCP server in PolicyLayer and add a rule for ssh_reject_plan: 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 Remote MCP Server. Nothing to install.
ssh_reject_plan is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the ssh_reject_plan 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 ssh_reject_plan. 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.
ssh_reject_plan is provided by the SSH Remote MCP Server MCP server (nqmn/adremote-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from SSH Remote MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
21 SSH Remote MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.