get_device_status
AI agents call get_device_status 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 tool name 'get_device_status' follows read-pattern naming conventions (get_*). Despite the empty description lowering confidence slightly, the tool appears to retrieve device status information from FortiManager without triggering changes, asset creation, deletion, or financial transactions. This is consistent with Read category operations in network management contexts.
From the tool's definition Tool name 'get_device_status' indicates a status query operation. No description provided, but the name pattern and context (centralized firewall policy management) suggest information retrieval without modification.
Attacks that exploit this kind of access
get_device_status. 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_device_status: 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_device_status 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_device_status 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_device_status. 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_device_status 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 →