AI agents call search_sessions 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 and retrieves existing network session data from Arkime's packet capture database. It performs read-only operations on captured traffic metadata with optional filtering parameters. There are no side effects, data mutations, destructive operations, or external system invocations.
From the tool's definition Tool description states 'Search Arkime sessions' and 'Returns summarized session data' with 'optional filtering' — core characteristics of data retrieval without modification. No language indicating data creation, modification, deletion, or external execution.
Attacks that exploit this kind of access
Search Arkime sessions with optional filtering. Returns summarized session data. 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 search_sessions: 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.
search_sessions 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 search_sessions 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 search_sessions. 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.
search_sessions 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 →