discovery_status
AI agents call discovery_status to retrieve information from Metis Public Health without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the name alone, 'discovery_status' appears to be a status-checking or informational tool that retrieves current state without modifying data. The empty description reduces confidence, but the naming convention aligns with Read operations typical in research/indexing systems like Metis. Without evidence of side effects, destructive actions, or code execution, Read is the most conservative classification.
From the tool's definition Tool name 'discovery_status' suggests querying or retrieving status information. The description is empty, providing no direct evidence of the tool's function.
Attacks that exploit this kind of access
discovery_status. 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 discovery_status: 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.
discovery_status 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 discovery_status 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 discovery_status. 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.
discovery_status 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.
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 →