Get user preferences from Supabase. If user_id is not provided, uses
AI agents call get_user_preferences to retrieve information from MCP BigQuery Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user preference data from a database without creating, modifying, deleting, or executing any operations. It is purely a read operation with minimal blast radius if misused by an AI agent—the worst case being unauthorized data access to user preferences, which is a confidentiality rather than availability or integrity risk.
From the tool's definition Tool name 'get_user_preferences' and description 'Get user preferences from Supabase' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get user preferences from Supabase. If user_id is not provided, uses. It is categorised as a Read tool in the MCP BigQuery Server MCP Server, which means it retrieves data without modifying state.
Register the MCP BigQuery Server MCP server in PolicyLayer and add a rule for get_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.
get_user_preferences 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_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 get_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.
get_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 →