ssh_execute_background · MCP Remote Access MCP

WHAT IT DOES

What ssh_execute_background does on MCP Remote Access

AI agents invoke ssh_execute_background to trigger actions in MCP Remote Access. 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 IT NEEDS A POLICY

Why ssh_execute_background needs a policy

This tool executes arbitrary shell commands on remote devices via SSH. While not inherently destructive, it enables arbitrary code execution on remote systems, which could modify data, access sensitive information, or compromise system integrity depending on what commands are executed. The background execution model and task monitoring suggest sustained command execution capability.

From the tool's definition Tool description explicitly states 'Execute a long-running command in the background' and 'command execution' is listed as a core capability.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ssh_execute_background Rate-limited

ssh_execute_background 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "ssh_execute_background": {
      "limits": [
        {
          "counter": "ssh_execute_background_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Remote Access, so you can run agents against it safely.

FAQ

Questions about ssh_execute_background

What does the ssh_execute_background tool do? +

Execute a long-running command in the background. Returns a task ID and output file path. Use ssh_check_background to monitor progress. It is categorised as a Execute tool in the MCP Remote Access MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on ssh_execute_background? +

Register the MCP Remote Access MCP server in PolicyLayer and add a rule for ssh_execute_background: 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 MCP Remote Access. Nothing to install.

What risk level is ssh_execute_background? +

ssh_execute_background is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit ssh_execute_background? +

Yes. Add a rate_limit block to the ssh_execute_background 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.

How do I block ssh_execute_background completely? +

Set action: deny in the PolicyLayer policy for ssh_execute_background. 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.

What MCP server provides ssh_execute_background? +

ssh_execute_background is provided by the MCP Remote Access MCP server (rfingadam/mcp-remote-access). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.