AI agents call get_preference_onboarding 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 | — | Stable user/profile id if already known. |
Parameters from the server's own tool schema.
This tool retrieves or presents onboarding questions to understand user consent before preferences are saved. It has no side effects beyond displaying questions and gathering user input. The actual preference saving is delegated to separate write operations (e.g., 'create_event_preference_profile').
From the tool's definition Tool is called 'get_preference_onboarding' and described as asking 'consent-first questions before saving event preferences.' The word 'get' and the onboarding/consent flow indicate data retrieval and questionnaire presentation, not storage or modification.
Attacks that exploit this kind of access
Use this when a user wants personalized event recommendations and UPlayground needs consent-first questions before saving event preferences. It is categorised as a Read tool in the Events MCP Server, which means it retrieves data without modifying state.
get_preference_onboarding accepts 1 parameter: 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 get_preference_onboarding: 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_preference_onboarding 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_preference_onboarding 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_preference_onboarding. 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_preference_onboarding 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_preference_onboarding 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 →