happ_test_case_delete
Удаляет тест-кейс (DELETE). История прошлых прогонов сохраняется (снапшоты).
This record as markdown: /tools/happ-ai-platform-mcp/happ-test-case-delete.md
What happ_test_case_delete does on Platform
AI agents call happ_test_case_delete to permanently remove resources in Platform, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
caseId | string | Yes | |
assistantId | string | Yes |
Parameters from the server's own tool schema.
Why happ_test_case_delete is rated Critical
The tool deletes a test case irreversibly. Although past run history (snapshots) is preserved, the test case itself is permanently removed. This matches the Destructive category. High severity because deleting test cases can disrupt QA workflows and cannot be undone for the case itself.
From the tool's definition Удаляет тест-кейс (DELETE) — tool name contains 'delete' and description explicitly states deletion via DELETE operation
Attacks that exploit this kind of access
The rule that runs happ_test_case_delete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Platform, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For happ_test_case_delete, this is the rule to start with:
happ_test_case_delete 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 Platform, apply this rule, and every happ_test_case_delete call is checked against it from then on.
Questions about happ_test_case_delete
Удаляет тест-кейс (DELETE). История прошлых прогонов сохраняется (снапшоты). It is categorised as a Destructive tool in the Platform MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
happ_test_case_delete accepts 2 parameters: caseId, assistantId. Required: caseId, assistantId. The full parameter table on this page comes from the server's own tool schema.
Register the Platform MCP server in PolicyLayer and add a rule for happ_test_case_delete: 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 Platform. Nothing to install.
happ_test_case_delete 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 happ_test_case_delete 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 happ_test_case_delete. 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.
happ_test_case_delete is provided by the Platform MCP server (@happ-ai/platform-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Platform, and thousands of servers like it.
Across the catalogue