AI agents use save_event_preferences 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 |
|---|---|---|---|
mode | string | — | |
consent | boolean | Yes | Must be true only after the user agreed to save preferences. |
profile_id | string | Yes | Stable user/profile id. |
preferences | object | Yes | |
profile_secret | string | Yes | Private profile secret returned when the profile was created. |
Parameters from the server's own tool schema.
This tool creates or modifies user preference data without deleting it and with no irreversible effects. The operations described (add, update, merge, replace) are all reversible modifications. While it modifies user data (slightly elevated severity), it does not execute code, trigger external operations, destroy data, or move money.
From the tool's definition Tool description explicitly states it is used to 'add, update, merge, or replace saved event preferences'—operations that modify user data reversibly.
Risk signalsHigh parameter count (16 properties)
Attacks that exploit this kind of access
Use this when a consenting user already has a UPlayground profile and wants to add, update, merge, or replace saved event preferences. 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.
save_event_preferences accepts 5 parameters: mode, consent, profile_id, preferences, profile_secret. Required: consent, profile_id, preferences, 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 save_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.
save_event_preferences 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 save_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 save_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.
save_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.
save_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 →