Delete a workflow status from a project
AI agents call delete_status to permanently remove resources in Tickr — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project slug |
status_id | string | Yes | Status ID to delete |
Parameters from the server's own tool schema.
This tool permanently removes a workflow status configuration from a project, which cannot be undone and may break workflows or lose status-related metadata. This is an irreversible destructive action with significant side effects on project operations, warranting the Destructive category and high severity.
From the tool's definition Tool name is 'delete_status' with description 'Delete a workflow status from a project' — the verb 'Delete' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a workflow status from a project. It is categorised as a Destructive tool in the Tickr MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
delete_status accepts 2 parameters: project, status_id. Required: project, status_id. The full parameter table on this page comes from the server's own tool schema.
Register the Tickr MCP server in PolicyLayer and add a rule for delete_status: 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 Tickr. Nothing to install.
delete_status 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_status 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_status. 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_status is provided by the Tickr MCP server (@k-system/tickr-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →