Store user preferences - what they like/dislike, how they want things done
AI agents use add_preference to create or update resources in Enhanced MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Enhanced MCP Server environment.
This tool creates or modifies user preference data in a persistent store (likely Google Drive, Sheets, or Keep based on server context). While preferences are typically non-critical metadata, storing user preferences without proper authorization or validation could enable preference injection attacks or unauthorized profiling.
From the tool's definition Tool name 'add_preference' and description 'Store user preferences' indicate creation/modification of user data. The action is reversible (preferences can be updated or deleted), with no irreversible data loss or financial impact.
Attacks that exploit this kind of access
Store user preferences - what they like/dislike, how they want things done. It is categorised as a Write tool in the Enhanced MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Enhanced MCP Server MCP server in PolicyLayer and add a rule for add_preference: 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 Enhanced MCP Server. Nothing to install.
add_preference 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 add_preference 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 add_preference. 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.
add_preference is provided by the Enhanced MCP Server MCP server (pbulbule13/mcpwithgoogle). 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 →