add_device

A write tool on the FortiManager MCP server.

SERVERFortiManager MCP Server SOURCErstierli/fortimanager-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/rstierli-fortimanager-mcp/add-device.md

WHAT IT DOES

What add_device does on FortiManager MCP Server

AI agents use add_device to create or update resources in FortiManager MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FortiManager MCP Server environment.

RISK

Why add_device is rated Medium

The tool creates new device entries in FortiManager, modifying the centralized configuration state. While reversible (devices can be removed), this is a Write operation with high blast radius in a security-critical context—unauthorized device additions could enable unauthorized network access, bypass controls, or establish persistence mechanisms.

From the tool's definition Tool name is 'add_device' which indicates creation of a device resource. Server context shows 'device provisioning' as a core capability. Sibling tool 'add_devices_bulk' confirms this is a Write operation for adding/creating devices.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs add_device safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FortiManager MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For add_device, this is the rule to start with:

add_device Rate-limited

add_device stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "add_device": {
      "limits": [
        {
          "counter": "add_device_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FortiManager MCP Server, apply this rule, and every add_device call is checked against it from then on.

FAQ

Questions about add_device

What does the add_device tool do? +

add_device is a write tool on the FortiManager MCP Server MCP server. It is categorised as a Write tool in the FortiManager MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_device? +

Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for add_device: 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 add_device? +

add_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit add_device? +

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

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

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

KEEP EXPLORING

More on FortiManager MCP Server, and thousands of servers like it.

This server

All 236 FortiManager MCP Server tools →

Across the catalogue

add-tag on Kanban MCP Server →kb_add on Persistent Kb → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →