add_model_device
A write tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/add-model-device.md
What add_model_device does on FortiManager MCP Server
AI agents use add_model_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.
Why add_model_device is rated Medium
This tool creates or adds a device model to FortiManager, which is a reversible write operation. While the description is empty (reducing confidence slightly), the tool name and context of FortiManager's device provisioning capabilities clearly indicate it modifies infrastructure configuration.
From the tool's definition Tool name 'add_model_device' combined with context of sibling tools (add_device, add_devices_bulk) that perform device provisioning; FortiManager is used for 'device provisioning and network configuration.' The 'add' prefix indicates data…
Attacks that exploit this kind of access
The rule that runs add_model_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_model_device, this is the rule to start with:
add_model_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.
The button opens the PolicyLayer dashboard: create your workspace, connect FortiManager MCP Server, apply this rule, and every add_model_device call is checked against it from then on.
Questions about add_model_device
add_model_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.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for add_model_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.
add_model_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_model_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.
Set action: deny in the PolicyLayer policy for add_model_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.
add_model_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.
More on FortiManager MCP Server, and thousands of servers like it.
This server
Across the catalogue