check_for_newer_evidence
A read tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/check-for-newer-evidence.md
What check_for_newer_evidence does on Metis Public Health
AI agents call check_for_newer_evidence 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 check_for_newer_evidence is rated Low
Likely reads evidence data without side effects; empty description reduces confidence but does not suggest destructive capability.
From the tool's definition uninformative description; tool name implies checking/querying for evidence
Attacks that exploit this kind of access
The rule that runs check_for_newer_evidence 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 check_for_newer_evidence, this is the rule to start with:
check_for_newer_evidence 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 check_for_newer_evidence call is checked against it from then on.
Questions about check_for_newer_evidence
check_for_newer_evidence 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 check_for_newer_evidence: 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.
check_for_newer_evidence 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 check_for_newer_evidence 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 check_for_newer_evidence. 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.
check_for_newer_evidence 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