remove_test_plan_item
Remove a test case from a test plan by item ID. Get item IDs from get_test_plan.
This record as markdown: /tools/dugynoo-huly-mcp/remove-test-plan-item.md
What remove_test_plan_item does on Huly
AI agents call remove_test_plan_item 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 remove_test_plan_item is rated Critical
This tool irreversibly deletes test case associations from test plans. While the underlying test case may persist elsewhere, the specific test plan item is removed and cannot be undone through normal operations. This fits the Destructive category (delete/purge operations that cannot be undone). High severity due to potential data loss in QA workflows where test plan integrity is critical.
From the tool's definition Tool name 'remove_test_plan_item' with verb 'Remove' and description explicitly states it removes a test case from a test plan. Removal is irreversible without recreation.
Attacks that exploit this kind of access
The rule that runs remove_test_plan_item 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 remove_test_plan_item, this is the rule to start with:
remove_test_plan_item 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 remove_test_plan_item call is checked against it from then on.
Questions about remove_test_plan_item
Remove a test case from a test plan by item ID. Get item IDs from get_test_plan. 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 remove_test_plan_item: 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.
remove_test_plan_item 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 remove_test_plan_item 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 remove_test_plan_item. 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.
remove_test_plan_item 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.
More on Huly, and thousands of servers like it.
Across the catalogue