install_device_settings
A execute tool on the Fortimanager MCP server.
This record as markdown: /tools/jmpijll-fortimanager-mcp/install-device-settings.md
What install_device_settings does on Fortimanager
AI agents invoke install_device_settings to trigger actions in Fortimanager. 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 install_device_settings is rated High
The name 'install_device_settings' strongly implies deploying or pushing configuration settings to a network device via FortiManager. In network management contexts, 'install' typically means applying configurations to live devices, which is an Execute-level action with high blast radius (misconfiguration could disrupt network operations). The description is empty, lowering confidence.
From the tool's definition Tool name 'install_device_settings' alongside sibling tools like 'abort_policy_install' and 'add_real_device' in a FortiManager context suggests pushing/deploying configuration to network devices.
Attacks that exploit this kind of access
The rule that runs install_device_settings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Fortimanager, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For install_device_settings, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Fortimanager, apply this rule, and every install_device_settings call is checked against it from then on.
Questions about install_device_settings
install_device_settings is a execute tool on the Fortimanager MCP server. It is categorised as a Execute tool in the Fortimanager MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Fortimanager 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. Nothing to install.
install_device_settings is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
install_device_settings 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.
More on Fortimanager, and thousands of servers like it.
Across the catalogue