Set or update user preferences in Supabase. If user_id is not provided, uses
AI agents use set_user_preferences to create or update resources in MCP BigQuery Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP BigQuery Server environment.
This tool modifies user preference data in a database (Supabase) but does not delete data irreversibly, execute code, move money, or perform highly destructive operations. The impact is limited to preference configuration, which can be changed again.
From the tool's definition Tool name 'set_user_preferences' and description 'Set or update user preferences' indicate creation or modification of data in Supabase. The verb 'set' and 'update' are characteristic of Write operations.
Attacks that exploit this kind of access
Set or update user preferences in Supabase. If user_id is not provided, uses. It is categorised as a Write tool in the MCP BigQuery Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP BigQuery 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 MCP BigQuery 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 MCP BigQuery Server MCP server (mousten/mcp-bigquery-server). 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 →