Update an existing CLI script.
AI agents use update_script 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.
This tool modifies existing CLI scripts reversibly, which is characteristic of a Write operation. However, the severity is high rather than medium because CLI scripts in a centralized firewall management system (FortiManager) can have significant blast radius if maliciously modified—they could alter security policies, network configurations, or device provisioning across an organization's infrastructure.
From the tool's definition Tool name 'update_script' and description 'Update an existing CLI script' indicate modification of existing data. The tool updates CLI scripts used in FortiManager for network configuration and firewall policy management.
Attacks that exploit this kind of access
Update an existing CLI script. 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 update_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.
update_script 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 update_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 update_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.
update_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 →