Delete an extra item registration
AI agents call delete_extra_registration to permanently remove resources in IIITH Mess MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool performs an irreversible deletion operation on user data (an extra meal registration). While the blast radius is limited to a single student's extra registration rather than institutional data, deletion cannot be undone without manual intervention. This meets the Destructive category definition of actions that 'cannot be undone' (delete).
From the tool's definition Tool name includes 'delete' and description states 'Delete an extra item registration' — this irreversibly removes a registration record from the mess system.
Attacks that exploit this kind of access
Delete an extra item registration. It is categorised as a Destructive tool in the IIITH Mess MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the IIITH Mess MCP Server MCP server in PolicyLayer and add a rule for delete_extra_registration: 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.
delete_extra_registration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_extra_registration 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 delete_extra_registration. 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.
delete_extra_registration 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 →