Delete a task by ID (v2 API).
AI agents call deleteTaskV2 to permanently remove resources in Lofty MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool permanently removes a task record from the Lofty CRM database. Deletion cannot be undone and represents data loss. This is a destructive operation with potentially significant impact on CRM records and workflow continuity, warranting high severity classification. An AI agent could mistakenly delete important tasks, causing loss of critical business information.
From the tool's definition Tool name contains "delete" and description explicitly states "Delete a task by ID". This is an irreversible operation that removes data from the CRM system.
Attacks that exploit this kind of access
Delete a task by ID (v2 API). It is categorised as a Destructive tool in the Lofty MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Lofty MCP Server MCP server in PolicyLayer and add a rule for deleteTaskV2: 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 Lofty MCP Server. Nothing to install.
deleteTaskV2 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 deleteTaskV2 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 deleteTaskV2. 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.
deleteTaskV2 is provided by the Lofty MCP Server MCP server (nerdsnipe-inc/lofty-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 →