Update your preferences
AI agents use update_preferences to create or update resources in IIITH Mess MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your IIITH Mess MCP Server environment.
This tool creates or modifies user data reversibly (Write category). It is not destructive since preference updates can be undone by updating again. It is not execute/read/financial since it concerns configuration rather than code execution, data retrieval, or payments.
From the tool's definition Tool name is 'update_preferences' with description 'Update your preferences'. In the context of a meal management system, preferences typically include dietary restrictions, meal choices, allergies, delivery preferences, or similar user-configurable settings.
Attacks that exploit this kind of access
Update your preferences. It is categorised as a Write tool in the IIITH Mess MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the IIITH Mess MCP Server MCP server in PolicyLayer and add a rule for update_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 IIITH Mess MCP Server. Nothing to install.
update_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 update_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 update_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.
update_preferences is provided by the IIITH Mess MCP Server MCP server (njp6969/iiith-mess-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 →