Get mess rates (in paise) for a meal on a date, grouped by category.
AI agents call mess_get_rates to retrieve information from IIITH Mess MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves meal rate information grouped by category for a specified date. It has no side effects, does not modify data, execute code, delete records, or commit financial transactions. It is purely informational and falls squarely into the Read category with low severity since the blast radius of misuse is minimal—an agent could only query rates without causing harm.
From the tool's definition Tool name 'mess_get_rates' and description 'Get mess rates' indicate a retrieval operation that queries meal pricing information. No modification, deletion, or execution of commands occurs.
Documented attack patterns abuse exactly the kind of access mess_get_rates gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IIITH Mess MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for mess_get_rates:
{
"version": "1",
"default": "deny",
"tools": {
"mess_get_rates": {}
}
} mess_get_rates is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get mess rates (in paise) for a meal on a date, grouped by category. It is categorised as a Read tool in the IIITH Mess MCP MCP Server, which means it retrieves data without modifying state.
Register the IIITH Mess MCP server in PolicyLayer and add a rule for mess_get_rates: 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. Nothing to install.
mess_get_rates 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 mess_get_rates 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 mess_get_rates. 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.
mess_get_rates is provided by the IIITH Mess MCP server (kallind/iiith-mess-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from IIITH Mess MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
45 IIITH Mess MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.