validate_claim

"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct....

SERVER19hz SOURCEhttps://gateway.pipeworx.io/19hz/mcp
Low RISK CLASS
Category Read
Parameters 11 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-pipeworx-io-19hz/validate-claim.md

What validate_claim does on 19hz

AI agents call validate_claim to retrieve information from 19hz without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
claim string Yes Natural-language factual claim, e.g., "Apple's FY2024 revenue was $400 billion" or "Microsoft made about $100B in profit last year".

Parameters from the server's own tool schema.

Why validate_claim is rated Low

validate_claim is purely informational: it queries authoritative data sources (SEC filings) and returns read-only verdicts with structured comparisons. It has no side effects, cannot modify data, execute code, or commit financial actions. This is a straightforward Read operation with low risk of misuse.

From the tool's definition Tool description states it performs "fact check", "verify the claim", and "claim verification against authoritative sources". It "Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported)" with citations and comparisons.

Questions about validate_claim

What does the validate_claim tool do? +

"Is it true that…" / "fact check" / "verify the claim that…" / "did X really…" / "was Y actually…" / "confirm or refute" / "true or false" — natural-language claim verification against authoritative sources. Use whenever the agent needs to check whether something a user said is factually correct. v1 supports company-financial claims (revenue, net income, cash position for public US companies) via SEC EDGAR + XBRL. Returns a verdict (confirmed / approximately_correct / refuted / inconclusive / unsupported), extracted structured form, actual value with pipeworx:// citation, and percent delta. Replaces 4–6 sequential calls (NL parsing → entity resolution → data lookup → numeric comparison). It is categorised as a Read tool in the 19hz MCP Server, which means it retrieves data without modifying state.

What parameters does validate_claim accept? +

validate_claim accepts 1 parameter: claim. Required: claim. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on validate_claim? +

Register the 19hz MCP server in PolicyLayer and add a rule for validate_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 19hz. Nothing to install.

What risk level is validate_claim? +

validate_claim is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit validate_claim? +

Yes. Add a rate_limit block to the validate_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.

How do I block validate_claim completely? +

Set action: deny in the PolicyLayer policy for validate_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.

What MCP server provides validate_claim? +

validate_claim is provided by the 19hz MCP server (https://gateway.pipeworx.io/19hz/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on 19hz, and thousands of servers like it.

This server

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 19hz's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.