Get performance statistics for a session: total actions, success/error counts, avg/min/max duration.
AI agents call get_session_stats to retrieve information from WebControl without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only queries and returns session statistics without creating, modifying, deleting, or executing any operations. It has no blast radius beyond information disclosure of performance data, which is typically non-sensitive. Classification as Read is appropriate with high confidence.
From the tool's definition get_session_stats retrieves performance statistics (total actions, success/error counts, avg/min/max duration) with no modification or side effects. The name 'get_' and description of retrieving aggregate metrics confirm a read-only operation.
Attacks that exploit this kind of access
Get performance statistics for a session: total actions, success/error counts, avg/min/max duration. It is categorised as a Read tool in the WebControl MCP Server, which means it retrieves data without modifying state.
Register the WebControl MCP server in PolicyLayer and add a rule for get_session_stats: 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 WebControl. Nothing to install.
get_session_stats 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_stats 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_stats. 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_stats is provided by the WebControl MCP server (matansht/webcontrol). 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 →