list_addresses
AI agents call list_addresses 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 'list_addresses' tool retrieves or queries address configuration data from FortiManager without modifying, deleting, or executing operations. The naming convention aligns with Read category semantics. While the empty description limits detail, the clear intent to enumerate addresses poses minimal risk; misuse would expose sensitive network data but not enable direct operational damage or resource consumption.
From the tool's definition Tool name 'list_addresses' indicates data retrieval. The verb 'list' is a classic Read operation pattern. Description is empty, but the tool name strongly suggests querying/enumerating address objects.
Attacks that exploit this kind of access
list_addresses. 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 list_addresses: 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.
list_addresses 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 list_addresses 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 list_addresses. 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.
list_addresses 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 →