delete_test_run

Permanently delete a test run. This does not delete associated test results. Cannot be undone.

SERVERHuly SOURCEdugynoo/huly-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dugynoo-huly-mcp/delete-test-run.md

WHAT IT DOES

What delete_test_run does on Huly

AI agents call delete_test_run to permanently remove resources in Huly, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_test_run is rated Critical

This tool irreversibly removes a test run record from the system. While the description notes that associated test results are not deleted, the permanent deletion of the test run itself with explicit 'Cannot be undone' language makes this a Destructive operation.

From the tool's definition Tool description explicitly states 'Permanently delete a test run' and 'Cannot be undone.' The irreversible deletion of data is the defining characteristic of the Destructive category.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_test_run safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Huly, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_test_run, this is the rule to start with:

delete_test_run Hidden

delete_test_run is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_test_run"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_test_run call is checked against it from then on.

FAQ

Questions about delete_test_run

What does the delete_test_run tool do? +

Permanently delete a test run. This does not delete associated test results. Cannot be undone. It is categorised as a Destructive tool in the Huly MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_test_run? +

Register the Huly MCP server in PolicyLayer and add a rule for delete_test_run: 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 Huly. Nothing to install.

What risk level is delete_test_run? +

delete_test_run is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_test_run? +

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

Set action: deny in the PolicyLayer policy for delete_test_run. 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 delete_test_run? +

delete_test_run is provided by the Huly MCP server (dugynoo/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Huly, and thousands of servers like it.

This server

All 218 Huly tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →