execute_script_on_device
A execute tool on the FortiManager MCP server.
This record as markdown: /tools/rstierli-fortimanager-mcp/execute-script-on-device.md
What execute_script_on_device does on FortiManager MCP Server
AI agents invoke execute_script_on_device 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 is rated High
Despite the empty description, the tool name unambiguously indicates remote code execution ('execute_script') on infrastructure devices ('on_device'). In the context of FortiManager (a centralized security and network management platform), this permits running arbitrary scripts on managed firewalls and network appliances.
From the tool's definition Tool name is 'execute_script_on_device' which explicitly indicates script execution on a network device. The FortiManager context involves centralized firewall and network device management, making script execution on managed devices a significant capability.
Attacks that exploit this kind of access
The rule that runs execute_script_on_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 execute_script_on_device, this is the rule to start with:
execute_script_on_device 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 call is checked against it from then on.
Questions about execute_script_on_device
execute_script_on_device is a execute tool on the FortiManager MCP Server MCP server. 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: 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 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 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. 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 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