create_script
AI agents invoke create_script 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.
Scripts on a FortiManager platform are typically executable automation artifacts that can run commands against managed devices. 'Create_script' likely creates a script object that can later be executed on firewalls, placing it in the Execute or Write category. Given the context of firewall management and that scripts imply execution capability, Execute is the most appropriate category.
From the tool's definition Tool name 'create_script' on a FortiManager server that manages firewall policies and network configuration via JSON-RPC API. Description is empty and uninformative.
Attacks that exploit this kind of access
create_script. 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 create_script: 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.
create_script 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 create_script 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 create_script. 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.
create_script 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →