AI agents call get_recent_events to retrieve information from Yocoolab without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves historical activity event data for inspection purposes. It has no side effects, does not execute code, does not modify any state, and does not delete or move data. The blast radius of misuse is minimal — an agent can only view event logs it is already authorized to access. This is a straightforward Read operation.
From the tool's definition Tool description states it 'Get[s] the most recent Claude Code activity events' and 'Shows timestamps, tool names, and key details' — purely retrieval/query operations with no modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Get the most recent Claude Code activity events (tool calls, prompts, errors). Shows timestamps, tool names, and key details. It is categorised as a Read tool in the Yocoolab MCP Server, which means it retrieves data without modifying state.
Register the Yocoolab MCP server in PolicyLayer and add a rule for get_recent_events: 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 Yocoolab. Nothing to install.
get_recent_events 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_recent_events 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_recent_events. 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_recent_events is provided by the Yocoolab MCP server (yocoolab/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_recent_events is one line of Yocoolab's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →