AI agents call unique_destinations to retrieve information from Arkime without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries existing packet capture data to enumerate unique destination IPs contacted by a host. It performs no write, delete, execute, or financial operations. The action is read-only analysis of captured network traffic, consistent with network monitoring and investigation use cases.
From the tool's definition Tool description states 'List distinct external destination IPs' — a query operation that retrieves and summarizes network data with no modification, deletion, or execution of commands.
Attacks that exploit this kind of access
List distinct external destination IPs contacted by an internal host. It is categorised as a Read tool in the Arkime MCP Server, which means it retrieves data without modifying state.
Register the Arkime MCP server in PolicyLayer and add a rule for unique_destinations: 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 Arkime. Nothing to install.
unique_destinations 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 unique_destinations 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 unique_destinations. 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.
unique_destinations is provided by the Arkime MCP server (swannman/arkime-mcp-server). 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 →