next_discovery_tip
AI agents call next_discovery_tip 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.
Given the tool name and the context of Metis as a research companion with a PDF library, this tool likely retrieves the next discovery tip from a curated set—a read operation with no side effects. The lack of description lowers confidence, but the naming pattern is consistent with Read-category tools. No evidence of execution, modification, deletion, or financial operations.
From the tool's definition Tool name 'next_discovery_tip' suggests retrieving the next suggestion or tip from a discovery system. No description provided to clarify intent.
Attacks that exploit this kind of access
next_discovery_tip. 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 next_discovery_tip: 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.
next_discovery_tip 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 next_discovery_tip 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 next_discovery_tip. 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.
next_discovery_tip 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 →