fortigate_run_readonly_command

WHAT IT DOES

What fortigate_run_readonly_command does on Fortigate MCP

AI agents invoke fortigate_run_readonly_command to trigger actions in Fortigate MCP. 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 fortigate_run_readonly_command needs a policy

This tool executes commands on Fortigate firewalls, which is an Execute operation. While constrained to read-only operations (mitigating severity from high to medium), the ability to run commands dynamically means outcomes depend on agent-supplied arguments and could impact system state or reveal sensitive diagnostic data.

From the tool's definition Tool name 'fortigate_run_readonly_command' indicates execution of commands against Fortigate firewalls via SSH. The server description mentions 'diagnostics' and 'natural language' querying, suggesting dynamic command execution.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

fortigate_run_readonly_command Rate-limited

fortigate_run_readonly_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": {
    "fortigate_run_readonly_command": {
      "limits": [
        {
          "counter": "fortigate_run_readonly_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 Fortigate MCP, so you can run agents against it safely.

FAQ

Questions about fortigate_run_readonly_command

What does the fortigate_run_readonly_command tool do? +

fortigate_run_readonly_command. It is categorised as a Execute tool in the Fortigate MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on fortigate_run_readonly_command? +

Register the Fortigate MCP server in PolicyLayer and add a rule for fortigate_run_readonly_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 Fortigate MCP. Nothing to install.

What risk level is fortigate_run_readonly_command? +

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

Can I rate-limit fortigate_run_readonly_command? +

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

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

fortigate_run_readonly_command is provided by the Fortigate MCP server (picaresco/mcp-fortigate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.