AI agents use create_event_preference_profile to create or update resources in Events — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Events environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
consent | boolean | Yes | Must be true only after the user agreed to save preferences. |
preferences | object | — |
Parameters from the server's own tool schema.
This tool creates a new user preference profile by storing event preferences when a user opts in. It is a reversible write operation that persists user configuration data. The blast radius is low—misuse would merely create or overwrite a user preference profile, which can be deleted or modified without consequences. No financial, destructive, or executable operations are involved.
From the tool's definition Tool description states 'save event preferences' and 'create...preference profile', indicating creation and storage of user data. No deletion, financial transaction, or code execution involved.
Risk signalsHigh parameter count (13 properties)
Attacks that exploit this kind of access
Use this when a user explicitly agrees to save event preferences and does not already have a UPlayground preference profile. It is categorised as a Write tool in the Events MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
create_event_preference_profile accepts 2 parameters: consent, preferences. Required: consent. 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 create_event_preference_profile: 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.
create_event_preference_profile is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_event_preference_profile 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 create_event_preference_profile. 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.
create_event_preference_profile 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.
create_event_preference_profile 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 →