execute_script_on_device_group
Execute a CLI script on a device group.
This record as markdown: /tools/rstierli-fortimanager-mcp/execute-script-on-device-group.md
What execute_script_on_device_group does on FortiManager MCP Server
AI agents invoke execute_script_on_device_group 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 execute_script_on_device_group is rated High
This tool executes CLI scripts on device groups, which is a classic Execute operation that runs arbitrary commands on network infrastructure. The blast radius is high because FortiManager controls firewall devices, and script execution could modify firewall rules, disable security controls, exfiltrate data, or disrupt network operations.
From the tool's definition Tool name contains 'execute_script' and description states 'Execute a CLI script on a device group' - directly indicates arbitrary code execution on network devices.
Attacks that exploit this kind of access
The rule that runs execute_script_on_device_group 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 execute_script_on_device_group, this is the rule to start with:
execute_script_on_device_group 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 MCP Server, apply this rule, and every execute_script_on_device_group call is checked against it from then on.
Questions about execute_script_on_device_group
Execute a CLI script on a device group. 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.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for execute_script_on_device_group: 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.
execute_script_on_device_group 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 execute_script_on_device_group 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 execute_script_on_device_group. 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.
execute_script_on_device_group 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.
Across the catalogue