Browse past events (both acknowledged and unacknowledged)
AI agents call get_event_history to retrieve information from ClawDaemon MCP 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 event history without side effects. While the broader server enables significant automation capabilities across 23 platforms, this specific tool is limited to passive data retrieval. The severity is low because viewing event history poses minimal risk—the blast radius is confined to information disclosure of event data already generated by the system.
From the tool's definition Tool description states 'Browse past events' with no mention of modifying, deleting, or executing actions. The verb 'browse' and context of reviewing 'acknowledged and unacknowledged' events indicate read-only retrieval of historical data.
Attacks that exploit this kind of access
Browse past events (both acknowledged and unacknowledged). It is categorised as a Read tool in the ClawDaemon MCP MCP Server, which means it retrieves data without modifying state.
Register the ClawDaemon MCP server in PolicyLayer and add a rule for get_event_history: 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 ClawDaemon MCP. Nothing to install.
get_event_history 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_event_history 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_event_history. 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_event_history is provided by the ClawDaemon MCP server (mordiaky/clawdaemon-mcp). 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 →