Submit anonymous feedback for a meal you
AI agents use submit_feedback 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 new feedback records in the mess management system. It is a Write operation because it creates or stores data reversibly—feedback can typically be deleted or modified. It has low severity because feedback submission has minimal blast radius: it cannot delete data, execute code, move money, or cause irreversible harm.
From the tool's definition Tool name 'submit_feedback' and description indicates it submits (creates) feedback data. The description states 'Submit anonymous feedback for a meal' which is a create/write operation that stores user feedback in the system.
Attacks that exploit this kind of access
Submit anonymous feedback for a meal you. 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 submit_feedback: 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.
submit_feedback 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 submit_feedback 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 submit_feedback. 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.
submit_feedback 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 →