Approve a preview and start full validation processing. job_id: the session_id value — "job_id" and "session_id" are the same string. approved_cost_usd MUST be provided and must match the estimated cost from the preview_complete response. This prevents accidental billing...
Part of the Hyperplexity MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use approve_validation to create or modify resources in Hyperplexity. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call approve_validation repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Hyperplexity.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
approve_validation:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Hyperplexity policy for all 16 tools.
Agents calling write-class tools like approve_validation have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Approve a preview and start full validation processing. job_id: the session_id value — "job_id" and "session_id" are the same string. approved_cost_usd MUST be provided and must match the estimated cost from the preview_complete response. This prevents accidental billing without first reviewing preview results and the cost estimate. Workflow: 1. Call wait_for_job to reach preview_complete — read the inline preview_table (3-row sample) and cost_estimate.estimated_total_cost_usd from the response 2. Call approve_validation(job_id=<session_id>, approved_cost_usd=<that value>) . It is categorised as a Write tool in the Hyperplexity MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for approve_validation. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Hyperplexity MCP server.
approve_validation is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the approve_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 approve_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.
approve_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