High-risk tools in Hyperplexity
5 of the 16 tools in Hyperplexity are classified as high risk. This page profiles those tools specifically, with recommended policy actions and the attack patterns that target them.
Every operation listed below is an action PolicyLayer recommends controlling at the transport layer. Open any tool to see the full profile, risk score, and YAML policy snippet.
Tools at high risk
-
start_reference_checkExecute 3/5Submit 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 o...
-
start_table_makerExecute 3/5Start a Table Maker conversation to generate a research table. Describe the table you want in natural language, e.g.: 'Create a table of AI startups that raised...
-
start_table_validationExecute 4/5Confirm the upload and detect matching prior configs. Call this immediately after upload_file. Returns config_matches with match_score — if score >= 0.85 a prio...
-
wait_for_conversationExecute 3/5Wait for a conversation turn to complete, emitting live synthetic progress. Preferred over manually polling get_conversation. Since conversation processing has ...
-
wait_for_jobExecute 4/5Wait for a job to reach a terminal state, emitting live MCP progress notifications. Preferred over manually looping get_job_status. The MCP host shows a live pr...
Attacks that target this class
High-risk tools in any server share these documented attack patterns. Each links to the full case and the defensive policy.
More on Hyperplexity
Enforce policy on Hyperplexity
One command generates a policy scaffold for every server in your MCP config.
npx -y @policylayer/intercept init