AI agents call get_attending_stats to retrieve information from Rewind without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and aggregates historical attendance data for analysis purposes. It performs a read-only query operation with no side effects, data modification, code execution, or financial implications. The aggregate nature of the output (counts by category/type/year) further confirms it is strictly informational.
From the tool's definition Tool name 'get_attending_stats' and description 'Aggregate counts of attended events broken down by category, event_type, and year' indicate a data retrieval operation that computes and returns aggregate statistics without modifying any data.
Attacks that exploit this kind of access
Aggregate counts of attended events broken down by category, event_type, and year. It is categorised as a Read tool in the Rewind MCP Server, which means it retrieves data without modifying state.
Register the Rewind MCP server in PolicyLayer and add a rule for get_attending_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 Rewind. Nothing to install.
get_attending_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_attending_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_attending_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_attending_stats is provided by the Rewind MCP server (rewind-mcp-server). 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 →