remote_fleet_command · Infra Ops MCP: Risk & Policy

WHAT IT DOES

What remote_fleet_command does on Infra Ops

AI agents invoke remote_fleet_command to trigger actions in Infra Ops. 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 remote_fleet_command needs a policy

This tool executes arbitrary commands on remote infrastructure via SSH. While not irreversible (Execute rather than Destructive), it can trigger external operations with effects dependent on the command arguments. The 'multiple remote hosts' aspect amplifies blast radius - a single misused invocation could affect many systems simultaneously.

From the tool's definition Tool description states 'Execute a command across multiple remote hosts via SSH' - the word 'Execute' combined with ability to run arbitrary commands on multiple machines via SSH indicates this is a code/command execution tool.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

remote_fleet_command Rate-limited

remote_fleet_command 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": {
    "remote_fleet_command": {
      "limits": [
        {
          "counter": "remote_fleet_command_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 Infra Ops, so you can run agents against it safely.

FAQ

Questions about remote_fleet_command

What does the remote_fleet_command tool do? +

Execute a command across multiple remote hosts via SSH. It is categorised as a Execute tool in the Infra Ops MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on remote_fleet_command? +

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

What risk level is remote_fleet_command? +

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

Can I rate-limit remote_fleet_command? +

Yes. Add a rate_limit block to the remote_fleet_command 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 remote_fleet_command completely? +

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

remote_fleet_command is provided by the Infra Ops MCP server (skyvanguard/infra-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.