get_attending_year_in_review

Year-in-review summary for attended events: totals, monthly breakdown, top venues, top concert performers, and the full event list. Use this when the user asks

Server Rewind rewind-mcp-server
Category Read
Risk class Low
Parameters 00 required

What get_attending_year_in_review does on Rewind

AI agents call get_attending_year_in_review 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.

Why get_attending_year_in_review needs a policy

This tool retrieves and aggregates historical event attendance data to present a summary view. It performs no mutations, does not execute code or external operations, and cannot delete or modify data. This is a straightforward read operation accessing pre-existing personal data. Severity is low because misuse would only expose personal attendance history without enabling further damage.

From the tool's definition Tool name 'get_attending_year_in_review' and description 'Year-in-review summary for attended events: totals, monthly breakdown, top venues, top concert performers, and the full event list' indicate data retrieval only.

Questions about get_attending_year_in_review

What does the get_attending_year_in_review tool do? +

Year-in-review summary for attended events: totals, monthly breakdown, top venues, top concert performers, and the full event list. Use this when the user asks. It is categorised as a Read tool in the Rewind MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_attending_year_in_review? +

Register the Rewind MCP server in PolicyLayer and add a rule for get_attending_year_in_review: 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.

What risk level is get_attending_year_in_review? +

get_attending_year_in_review is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_attending_year_in_review? +

Yes. Add a rate_limit block to the get_attending_year_in_review 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.

How do I block get_attending_year_in_review completely? +

Set action: deny in the PolicyLayer policy for get_attending_year_in_review. 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.

What MCP server provides get_attending_year_in_review? +

get_attending_year_in_review 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.