delete_test_result
Permanently delete a test result. Cannot be undone.
This record as markdown: /tools/io-github-dearlordylord-huly-mcp/delete-test-result.md
What delete_test_result does on Huly
AI agents call delete_test_result 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.
Why delete_test_result is rated Critical
This tool irreversibly removes data (a test result) with no possibility of recovery or undo. This matches the Destructive category definition. Severity is high because deletion of test results could impact project history, compliance records, and audit trails, though the blast radius is somewhat limited to the specific test result domain rather than affecting financial systems or broad user data.
From the tool's definition Tool description explicitly states 'Permanently delete a test result. Cannot be undone.' The words 'Permanently delete' and 'Cannot be undone' directly indicate irreversible data destruction.
Attacks that exploit this kind of access
The rule that runs delete_test_result 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_result, this is the rule to start with:
delete_test_result is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Huly, apply this rule, and every delete_test_result call is checked against it from then on.
Questions about delete_test_result
Permanently delete a test result. 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.
Register the Huly MCP server in PolicyLayer and add a rule for delete_test_result: 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.
delete_test_result is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_test_result 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.
Set action: deny in the PolicyLayer policy for delete_test_result. 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.
delete_test_result is provided by the Huly MCP server (@firfi/huly-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Huly, and thousands of servers like it.
Across the catalogue