AI agents call get_session_detail 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 returns existing session metadata and decoded protocol details from captured network traffic. It has no side effects—it does not create, modify, delete, or execute any operations. The data it accesses is already captured and immutable in the archive. Even if misused by an AI agent, it can only expose information; it cannot alter network captures, delete data, or trigger external actions.
From the tool's definition Tool retrieves 'full detail for a single session including decoded protocol information' from Arkime packet capture system. The verb 'Get' and action 'retrieve' indicate data retrieval with no modification or deletion capability.
Attacks that exploit this kind of access
Get full detail for a single session including decoded protocol information. 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 get_session_detail: 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.
get_session_detail 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_session_detail 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_session_detail. 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_session_detail 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 →