discovery_intro
Return the tiny first-run orientation — the 3-5 highest-value capabilities.
This record as markdown: /tools/sveritg-metis-ph/discovery-intro.md
What discovery_intro does on Metis Public Health
AI agents call discovery_intro 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 discovery_intro is rated Low
This tool simply retrieves and returns static informational content (an orientation/intro message). It has no side effects, does not modify data, and cannot cause harm if misused. It is a pure read operation.
From the tool's definition Return the tiny first-run orientation — the 3-5 highest-value capabilities.
Attacks that exploit this kind of access
The rule that runs discovery_intro 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 discovery_intro, this is the rule to start with:
discovery_intro 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 discovery_intro call is checked against it from then on.
Questions about discovery_intro
Return the tiny first-run orientation — the 3-5 highest-value capabilities. 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_intro: 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_intro 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_intro 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_intro. 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_intro 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