get_preview_result
AI agents call get_preview_result to retrieve information from FortiManager MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get_preview_result' function follows standard read operation patterns (get_*) and logically would retrieve pre-computed or simulated results without modifying system state. In the context of FortiManager, preview operations typically show what would happen before actual changes are applied. This is consistent with Read category behavior.
From the tool's definition Tool name 'get_preview_result' indicates a retrieval operation to fetch results of a preview (likely a dry-run or simulation). No description provided, but naming convention suggests read-only data retrieval.
Attacks that exploit this kind of access
get_preview_result. 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_preview_result: 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_preview_result 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_preview_result 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_preview_result. 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_preview_result 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 →