Get all your meal registrations in a date range (max 2 months)
AI agents call get_registrations to retrieve information from IIITH Mess MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing meal registration data for a user within a specified date range. It performs a read-only operation with no capability to modify, delete, or execute external actions. The data retrieved is already scoped to the user's own registrations and a bounded time window (max 2 months), minimizing blast radius. Classification as Read with low severity is appropriate.
From the tool's definition Tool name 'get_registrations' and description 'Get all your meal registrations in a date range' indicate a retrieval operation with no modifications, deletions, or side effects.
Attacks that exploit this kind of access
Get all your meal registrations in a date range (max 2 months). It is categorised as a Read tool in the IIITH Mess MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IIITH Mess MCP Server MCP server in PolicyLayer and add a rule for get_registrations: 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.
get_registrations 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_registrations 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_registrations. 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_registrations 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 →