AI agents call geo_summary 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 performs read-only analysis and aggregation of network traffic data by geographic origin/destination. It retrieves summary statistics without modifying, executing operations, or deleting data. The minimal sensitivity of geolocation summaries and lack of side effects places this in the Read category with low severity.
From the tool's definition Tool name 'geo_summary' and description 'Breakdown of destination traffic by country' indicate a query operation that retrieves and summarizes geolocation statistics from existing packet capture data.
Attacks that exploit this kind of access
Breakdown of destination traffic by country. Highlights where your traffic. 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 geo_summary: 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.
geo_summary 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 geo_summary 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 geo_summary. 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.
geo_summary 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 →