verify_claim
A read tool on the Metis Public Health MCP server.
This record as markdown: /tools/sveritg-metis-ph/verify-claim.md
What verify_claim does on Metis Public Health
AI agents call verify_claim 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 verify_claim is rated Low
Based on the tool name alone, 'verify_claim' most likely reads or checks a claim for validity, which is a read/query operation with no side effects. Context from sibling tools (e.g., 'decode_signed', 'attested_reputation', 'check_media_signals') supports a pattern of verification and read operations.
From the tool's definition Tool name 'verify_claim' suggests validation/verification of a claim; description is empty and uninformative.
Attacks that exploit this kind of access
The rule that runs verify_claim 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 verify_claim, this is the rule to start with:
verify_claim 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 verify_claim call is checked against it from then on.
Questions about verify_claim
verify_claim 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 verify_claim: 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.
verify_claim 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 verify_claim 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 verify_claim. 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.
verify_claim 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