AI agents call get_event_preferences 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 |
|---|---|---|---|
profile_id | string | Yes | Stable user/profile id. |
profile_secret | string | Yes | Private profile secret returned when the profile was created. |
Parameters from the server's own tool schema.
This tool queries and retrieves existing user preference data. The verb 'view' and the absence of any creation, modification, deletion, or external triggering language confirms this is a Read operation. The data returned is user preferences and recommendation signals, which poses minimal security risk if misused — no financial, destructive, or system-level impact.
From the tool's definition Tool description states 'view saved event preferences or learned recommendation signals' — retrieval of user profile data with no modification or side effects.
Attacks that exploit this kind of access
Use this when a user with a UPlayground profile wants to view saved event preferences or learned recommendation signals. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
get_event_preferences accepts 2 parameters: profile_id, profile_secret. Required: profile_id, profile_secret. 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_preferences: 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_preferences 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_preferences 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_preferences. 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_preferences 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_preferences 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 →