High Risk →

start_table_validation

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 ...

Risk signalsAccepts file system path (filename)

Part of the Hyperplexity server.

start_table_validation can trigger actions in Hyperplexity, with no limits today. PolicyLayer puts allow, deny, and rate-limit rules on every call. Live in minutes.

SECURE HYPERPLEXITY →

Free to start. No card required.

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. 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "start_table_validation": {
      "limits": [
        {
          "counter": "start_table_validation_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

See the full Hyperplexity policy for all 16 tools.

Get this rule live on your own Hyperplexity server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HYPERPLEXITY →

View all 16 tools →

These attack patterns abuse exactly the kind of access start_table_validation gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so start_table_validation only ever does what you allow.

SECURE HYPERPLEXITY →

Other execute tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.

What does the start_table_validation tool do? +

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.

How do I enforce a policy on start_table_validation? +

Register the Hyperplexity MCP server in PolicyLayer and add a rule for start_table_validation: 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.

What risk level is start_table_validation? +

start_table_validation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit start_table_validation? +

Yes. Add a rate_limit block to the start_table_validation 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 start_table_validation completely? +

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

What MCP server provides start_table_validation? +

start_table_validation 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.

Enforce policy on every Hyperplexity tool call.

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.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.