AI agents call plan_night 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 | — | City name, for example berlin or new york. |
free | boolean | — | |
vibe | array | — | |
when | string | — | Date preset: today, tonight, tomorrow, weekend, week, this week, any, or YYYY-MM-DD. |
avoid | array | — | Terms to penalize in recommendations. |
limit | number | — | Results per page (default 12). The response's count field is the TOTAL matching events — raise limit or use offset to page through more. |
pride | boolean | — | |
query | string | — | Keyword search. |
venue | string | — | |
genres | array | — | |
offset | number | — | |
date_to | string | — | Inclusive end date in YYYY-MM-DD format. |
Parameters from the server's own tool schema.
The tool appears to retrieve and aggregate event options into a plan. There is no indication it creates, modifies, purchases, or executes anything; it surfaces recommendations from existing inventory. Confidence is slightly reduced because the description is vague about whether it triggers any booking or reservation side effects, but the framing as a 'plan' rather than a booking action suggests read-only behavior.
From the tool's definition 'compact night-out plan with a primary live event option and fallback options from UPlayground inventory' — the tool generates a plan/recommendation by querying available events
Risk signalsHigh parameter count (20 properties)
Attacks that exploit this kind of access
Use this when a user wants a compact night-out plan with a primary live event option and fallback options from UPlayground inventory. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
plan_night accepts 12 parameters: city, free, vibe, when, avoid, limit, pride, query, venue, genres, offset, date_to. 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 plan_night: 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.
plan_night 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 plan_night 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 plan_night. 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.
plan_night 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.
plan_night 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 →