get_script
Get details of a specific CLI script.
This record as markdown: /tools/rstierli-fortimanager-mcp/get-script.md
What get_script does on FortiManager MCP Server
AI agents call get_script to retrieve information from FortiManager MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_script is rated Low
This tool retrieves metadata and details about an existing CLI script in FortiManager. It performs a read-only query operation without executing, modifying, or deleting any data. The verb 'Get' combined with 'details of' confirms a passive information retrieval action.
From the tool's definition Tool name 'get_script' with description 'Get details of a specific CLI script' indicates a retrieval operation with no modification or execution of the script itself.
Attacks that exploit this kind of access
The rule that runs get_script 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 get_script, this is the rule to start with:
get_script is read-only, so it stays allowed. 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 get_script call is checked against it from then on.
Questions about get_script
Get details of a specific CLI script. It is categorised as a Read tool in the FortiManager MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FortiManager MCP Server MCP server in PolicyLayer and add a rule for get_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.
get_script is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_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 get_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.
get_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.
More on FortiManager MCP Server, and thousands of servers like it.
This server
Across the catalogue