"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....
AI agents call validate_claim to retrieve information from Mcp Weather Gc Ca without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
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.
This tool retrieves and queries existing data to validate claims. It has no side effects—it does not create, modify, delete, or execute code. Even though it operates on financial data (company claims via SEC filings), it only reads and compares against authoritative sources. The tool poses minimal risk if misused by an AI agent, as it cannot move money, alter records, or trigger external operations.
From the tool's definition Tool performs fact-checking and claim verification against authoritative sources (SEC EDGAR + XBRL). Returns verdicts and citations without modifying, deleting, or executing operations.
Attacks that exploit this kind of access
"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 Mcp Weather Gc Ca MCP Server, which means it retrieves data without modifying state.
validate_claim accepts 1 parameter: claim. Required: claim. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Weather Gc Ca 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 Mcp Weather Gc Ca. Nothing to install.
validate_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 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.
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.
validate_claim is provided by the Mcp Weather Gc Ca MCP server (https://gateway.pipeworx.io/weather-gc-ca/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →