failover_cluster

THE RISK

Low Risk

Why failover_cluster needs a policy

The description is empty, making it impossible to determine the exact action. The name 'failover_cluster' suggests it may trigger or configure a failover operation on a network cluster, which could be Execute or Write in nature. However, without any description, confidence is very low.

From the tool's definition Tool name is 'failover_cluster' with empty description. No description provided to determine what the tool does.

Documented attack patterns abuse exactly the kind of access failover_cluster gives an agent:

POLICY

How to control failover_cluster

PolicyLayer is an MCP gateway — it sits between your AI agents and Fortimanager, and nothing reaches the server without passing your rules. This is the rule we recommend for failover_cluster:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "failover_cluster": {
      "limits": [
        {
          "counter": "failover_cluster_rate",
          "window": "minute",
          "max": 60,
          "scope": "grant"
        }
      ]
    }
  }
}

failover_cluster gets a rate cap, and everything else on the server is denied unless you say otherwise.

Create a free account and register Fortimanager — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

SET A RULE FOR THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Fortimanager tools

Destructive bulk_delete_security_profile_entries bulk_delete_security_profile_entries Destructive clear_database_cache clear_database_cache Destructive delete_adom_revision delete_adom_revision Destructive delete_central_dnat_policy Delete a central DNAT policy. Destructive delete_central_snat_policy Delete a central SNAT policy. Destructive delete_certificate_template delete_certificate_template Destructive delete_cli_script delete_cli_script Destructive delete_cli_template Delete a CLI template.

All 584 Fortimanager tools →

Other tools on other servers

Android Forensics ADB MCP Server generate_app_analysis_report Ethereum Tools add Math MCP Server complex_analysis_suite Crypto_MCP aes_encrypt

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Tool risk categories → How PolicyLayer classifies MCP tools by what they can do.
MCP tool → What an MCP tool is and how clients discover and call it.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about failover_cluster

What does the failover_cluster tool do? +

failover_cluster. It is categorised as a Other tool in the Fortimanager MCP Server, which means it performs auxiliary operations.

How do I enforce a policy on failover_cluster? +

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

What risk level is failover_cluster? +

failover_cluster is a Other tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit failover_cluster? +

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

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

failover_cluster is provided by the Fortimanager MCP server (jmpijll/fortimanager-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Fortimanager tool call.

Start from Fortimanager, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →