Paginate the append-only event log. Returns events and a nextCursor to pass as afterId on the next call.
AI agents call list_events_since to retrieve information from State Trace without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries historical events from an append-only log and returns paginated results with pagination cursors. It performs no write, delete, execute, or financial operations. The worst-case misuse scenario (an agent exhaustively reading event logs) has minimal blast radius and causes no data loss or state changes. Classified as Read/low severity.
From the tool's definition Tool description states it 'Paginate[s] the append-only event log. Returns events and a nextCursor' — a pure retrieval operation with no mutation or side effects. The verb 'list' and 'paginate' confirm read-only semantics.
Attacks that exploit this kind of access
Paginate the append-only event log. Returns events and a nextCursor to pass as afterId on the next call. It is categorised as a Read tool in the State Trace MCP Server, which means it retrieves data without modifying state.
Register the State Trace MCP server in PolicyLayer and add a rule for list_events_since: 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 State Trace. Nothing to install.
list_events_since 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 list_events_since 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 list_events_since. 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.
list_events_since is provided by the State Trace MCP server (agent-pattern-labs/state-trace). 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 →