Get the action history for a session. Shows what actions were performed, their timing, and success/failure.
AI agents call get_session_activity 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 retrieves and queries session action history—timing, actions performed, and their outcomes. It has no side effects, does not modify data, execute code, or trigger external operations. It is purely informational, making it a Read operation with low severity.
From the tool's definition Tool name 'get_session_activity' and description 'Get the action history for a session. Shows what actions were performed, their timing, and success/failure.' indicate retrieval of historical data without modification or side effects.
Attacks that exploit this kind of access
Get the action history for a session. Shows what actions were performed, their timing, and success/failure. 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_activity: 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_activity 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_activity 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_activity. 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_activity 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 →