Confirm the upload and detect matching prior configs. Call this immediately after upload_file. Returns config_matches with match_score — if score >= 0.85 a prior config can be reused directly. instructions: Optional natural-language description of what to validate ...
Accepts file system path (filename)
Part of the Hyperplexity MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents invoke start_table_validation 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_table_validation can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept 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.
tools:
start_table_validation:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full Hyperplexity policy for all 16 tools.
Agents calling execute-class tools like start_table_validation have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
start_table_validation is one of the high-risk operations in Hyperplexity. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.
Confirm the upload and detect matching prior configs. Call this immediately after upload_file. Returns config_matches with match_score — if score >= 0.85 a prior config can be reused directly. instructions: Optional natural-language description of what to validate and how (e.g. "This table lists clinical trials — validate that trial IDs, phase, and primary endpoints are accurate"). When provided, the upload interview is bypassed: the AI reads the table structure + instructions and generates a config directly without asking clarifying questions. Preview is auto-triggered immediately after. config_id: Optional ID of a known prior configuration to reuse directly. When provided, skips matching and the interview entirely — applies the config and queues the preview immediately. Response includes preview_queued=true and job_id. Use when you already know the config_id (e.g. from a previous job's get_results response). Config generation and the 3-row preview are free. Full validation is charged at approve_validation — you still see the cost at preview_complete before anything is billed. If balance is insufficient at that point, approve_validation returns an insufficient_balance error. . 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.
Add a rule in your Intercept YAML policy under the tools section for start_table_validation. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hyperplexity MCP server.
start_table_validation 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_table_validation rule in your Intercept 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 Intercept policy for start_table_validation. 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_table_validation is provided by the Hyperplexity MCP server (hyperplexity/hyperplexity). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept