mess_get_scans_count

THE RISK

Low Risk

Why mess_get_scans_count needs a policy

This tool retrieves meal scan count statistics—purely informational data with no capability to modify, delete, or execute actions. It has minimal blast radius if misused by an agent, as it only exposes aggregate meal attendance data. The lack of authentication requirement actually reduces sensitive exposure compared to individual user data, and the tool cannot affect billing, registrations, or account state.

From the tool's definition Tool name 'mess_get_scans_count' and description 'Get meal availment (scan) count for a mess on a date' indicate retrieval of historical or summary data. The phrase 'Get' and 'count' denote read-only query operations.

Documented attack patterns abuse exactly the kind of access mess_get_scans_count gives an agent:

POLICY

How to control mess_get_scans_count

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_scans_count:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "mess_get_scans_count": {}
  }
}

mess_get_scans_count is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register IIITH Mess MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More IIITH Mess MCP tools

Destructive mess_cancel_registration mess_cancel_registration Destructive mess_delete_auth_key Delete an auth key by its name (not its value). Identified by name in the URL path. Destructive mess_delete_extra_registration Delete an extra registration by its ID (passed as query param). Destructive mess_delete_monthly_registration Delete a monthly mess registration (individual meal registrations are kept). Execute mess_login_msit Login as an MSIT student or intern using email + password. Write mess_reset_qr_token Reset the user's QR code token (shown at the mess counter). Write mess_provide_feedback Submit anonymous feedback for a meal. User must have availed the meal. Write mess_skip_meal Mark a registration as skipped or unskipped.

All 45 IIITH Mess MCP tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about mess_get_scans_count

What does the mess_get_scans_count tool do? +

Get meal availment (scan) count for a mess on a date. No authentication required. It is categorised as a Read tool in the IIITH Mess MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mess_get_scans_count? +

Register the IIITH Mess MCP server in PolicyLayer and add a rule for mess_get_scans_count: 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.

What risk level is mess_get_scans_count? +

mess_get_scans_count is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit mess_get_scans_count? +

Yes. Add a rate_limit block to the mess_get_scans_count 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.

How do I block mess_get_scans_count completely? +

Set action: deny in the PolicyLayer policy for mess_get_scans_count. 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.

What MCP server provides mess_get_scans_count? +

mess_get_scans_count 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.

Enforce policy on every IIITH Mess MCP tool call.

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.

CHECK YOUR STACK →