Get a single attended event (sports game, concert, theater show) in full detail, including venue, tickets, and per-player stat lines for sports games. Renders the rich inline event card — linescore, top performers with photos, ticket info — in MCP Apps hosts. Use this when the user asks about ONE...
AI agents call get_attended_event 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 queries personal attendance history and returns event details including venue information, ticket data, and sports statistics. It performs only retrieval operations (get_attended_event) consistent with other Read-category tools on this server (get_article, get_artist_details, get_album_details). There is no creation, modification, deletion, code execution, or financial transaction involved.
From the tool's definition Tool description explicitly states 'Get a single attended event' and 'Renders the rich inline event card' — retrieves and displays personal event data without modification.
Attacks that exploit this kind of access
Get a single attended event (sports game, concert, theater show) in full detail, including venue, tickets, and per-player stat lines for sports games. Renders the rich inline event card — linescore, top performers with photos, ticket info — in MCP Apps hosts. Use this when the user asks about ONE specific event:. 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_attended_event: 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_attended_event 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_attended_event 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_attended_event. 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_attended_event 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 →