AI agents call get_event 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 |
|---|---|---|---|
id | string | Yes | Event id. |
Parameters from the server's own tool schema.
The tool retrieves event details based on an event ID. This is a read-only query operation with no side effects, no data modification, no code execution, and no financial transaction capability. The minimal severity reflects that event details are typically public information with no sensitive data exposure risk or blast radius if misused.
From the tool's definition Tool description states 'Use this when a user asks for details about a specific UPlayground event id' — this is a retrieval operation that fetches event information by ID without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
Use this when a user asks for details about a specific UPlayground event id returned by search, recommendations, or a night plan. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
get_event accepts 1 parameter: id. Required: 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 get_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 Events. Nothing to install.
get_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_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_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_event 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.
get_event 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 →