scan_inbox
A read tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/scan-inbox.md
What scan_inbox does on Metis Public Health
AI agents call scan_inbox to retrieve information from Metis Public Health without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why scan_inbox is rated Low
The tool is named 'scan_inbox', which typically involves reading or listing messages rather than modifying, deleting, or executing external operations. In the context of a research companion that indexes user data locally, scanning an inbox would retrieve information for analysis.
From the tool's definition Tool name 'scan_inbox' suggests retrieving or querying messages/items from an inbox; no destructive operations implied by 'scan'.
Attacks that exploit this kind of access
The rule that runs scan_inbox safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Metis Public Health, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For scan_inbox, this is the rule to start with:
scan_inbox is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Metis Public Health, apply this rule, and every scan_inbox call is checked against it from then on.
Questions about scan_inbox
scan_inbox is a read tool on the Metis Public Health MCP server. It is categorised as a Read tool in the Metis Public Health MCP Server, which means it retrieves data without modifying state.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for scan_inbox: 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 Metis Public Health. Nothing to install.
scan_inbox 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 scan_inbox 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 scan_inbox. 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.
scan_inbox is provided by the Metis Public Health MCP server (sveritg/metis_ph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Metis Public Health, and thousands of servers like it.
This server
Across the catalogue