AI agents call recommend_events_for_user to retrieve information from Events without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
city | string | — | |
vibe | array | — | |
when | string | — | |
limit | number | — | |
query | string | — | |
genres | array | — | |
date_to | string | — | |
date_from | string | — | |
price_max | number | — | |
profile_id | string | Yes | |
event_types | array | — | |
result_limit | number | — |
Parameters from the server's own tool schema.
This tool retrieves and returns event recommendations tailored to a user's preferences. It queries existing data (events, user profiles, preference profiles) and returns results without modifying any data, executing code, deleting anything, or moving money. The recommendation output is informational only. Even if recommendations are personalized, the operation remains a read-only retrieval.
From the tool's definition Tool description states it 'wants personalized event recommendations' which retrieves data based on user preferences; the method is passive (recommend, get) with no indication of creating, modifying, deleting, or executing external operations.
Risk signalsHigh parameter count (14 properties)
Attacks that exploit this kind of access
Use this when a user has a UPlayground preference profile and wants personalized event recommendations for tonight, this week, this weekend, or another date range. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
recommend_events_for_user accepts 12 parameters: city, vibe, when, limit, query, genres, date_to, date_from, price_max, profile_id, event_types, result_limit. Required: profile_id. The full parameter table on this page comes from the server's own tool schema.
Register the Events MCP server in PolicyLayer and add a rule for recommend_events_for_user: 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 Events. Nothing to install.
recommend_events_for_user 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 recommend_events_for_user 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 recommend_events_for_user. 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.
recommend_events_for_user is provided by the Events MCP server (uplayground-events). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
recommend_events_for_user is one line of Events's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →