Sets user preferences
AI agents use set_user_preferences to create or update resources in Red Bee MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Red Bee MCP Server environment.
This tool modifies user configuration data reversibly (preferences can be changed again). It does not execute arbitrary code, delete data, or move money. The blast radius is medium because preference changes affect the user's experience but are non-destructive and can be undone. Confidence is slightly reduced due to the generic description lacking specifics about what preferences can be modified.
From the tool's definition Tool name 'set_user_preferences' and description 'Sets user preferences' indicate a modification operation that creates or updates user preference data in the streaming platform.
Attacks that exploit this kind of access
Sets user preferences. It is categorised as a Write tool in the Red Bee MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Red Bee MCP Server MCP server in PolicyLayer and add a rule for set_user_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 Red Bee MCP Server. Nothing to install.
set_user_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 set_user_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 set_user_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.
set_user_preferences is provided by the Red Bee MCP Server MCP server (tamsi/redbee-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →