run_metis
A execute tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/run-metis.md
What run_metis does on Metis Public Health
AI agents invoke run_metis to trigger actions in Metis Public Health. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why run_metis is rated High
Despite empty description, the tool name 'run_metis' combined with the server's role as a research companion that routes to specialist agents indicates this tool likely executes code, queries, or external operations. Without explicit limiting language, the agent-routing and execution semantics warrant Execute classification.
From the tool's definition Tool named 'run_metis' with no description provided. Context indicates Metis routes requests to 34 specialist agents and performs analysis/aggregation operations.
Attacks that exploit this kind of access
The rule that runs run_metis 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 run_metis, this is the rule to start with:
run_metis stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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 run_metis call is checked against it from then on.
Questions about run_metis
run_metis is a execute tool on the Metis Public Health MCP server. It is categorised as a Execute tool in the Metis Public Health MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metis Public Health MCP server in PolicyLayer and add a rule for run_metis: 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.
run_metis is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the run_metis 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 run_metis. 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.
run_metis 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.
Across the catalogue