install_device_settings · FortiManager MCP Server MCP

WHAT IT DOES

What install_device_settings does on FortiManager MCP Server

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

The tool name suggests it pushes/installs configuration settings to network devices (firewalls), which is an active operation with external side effects on network infrastructure. However, the description is empty, so confidence is reduced.

From the tool's definition Tool name 'install_device_settings' on a FortiManager server that handles 'device provisioning and network configuration'. Sibling tools include assign and install operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

install_device_settings Rate-limited

install_device_settings 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": {
    "install_device_settings": {
      "limits": [
        {
          "counter": "install_device_settings_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 FortiManager MCP Server, so you can run agents against it safely.

FAQ

Questions about install_device_settings

What does the install_device_settings tool do? +

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

How do I enforce a policy on install_device_settings? +

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

What risk level is install_device_settings? +

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

Can I rate-limit install_device_settings? +

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

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

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