Submit a reference-check job to fact-check text or a document. For inline text: start_reference_check(text="The claims to fact-check...") For a PDF or document, upload it first then pass the s3_key: upload_file(file_path, file_type="pdf") → returns s3_key start_reference_check(s3_key=s3_key) Do N...
Part of the Hyperplexity server.
Free to start. No card required.
AI agents invoke start_reference_check to trigger processes or run actions in Hyperplexity. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
start_reference_check can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. PolicyLayer enforces rate limits and validates arguments to keep execution within safe bounds.
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
{
"version": "1",
"default": "deny",
"tools": {
"start_reference_check": {
"limits": [
{
"counter": "start_reference_check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}See the full Hyperplexity policy for all 16 tools.
These attack patterns abuse exactly the kind of access start_reference_check gives an agent. Each links to the full case and the policy that stops it:
Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Submit a reference-check job to fact-check text or a document. For inline text: start_reference_check(text="The claims to fact-check...") For a PDF or document, upload it first then pass the s3_key: upload_file(file_path, file_type="pdf") → returns s3_key start_reference_check(s3_key=s3_key) Do NOT call start_table_validation for PDFs — that starts the table validation pipeline, which is not what you want for a reference check. Designed for text with 4 or more factual claims; fewer claims may produce low-quality results. Three phases: - Phase 1 (free): claim extraction + 3-row preview validation (auto-triggered). wait_for_job blocks until status=preview_complete. Review preview_table (3 validated sample claims) and cost_estimate. - Approval gate: call approve_validation to proceed. - Phase 2 (charged): full claim validation. Returns XLSX, viewer URL, metadata. Set auto_approve=True to skip the approval gate and run straight through to completion automatically.. It is categorised as a Execute tool in the Hyperplexity MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Hyperplexity MCP server in PolicyLayer and add a rule for start_reference_check: 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 Hyperplexity. Nothing to install.
start_reference_check 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 start_reference_check 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 start_reference_check. 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.
start_reference_check is provided by the Hyperplexity MCP server (hyperplexity/hyperplexity). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Hyperplexity tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.