Delete an Asana task.
AI agents call delete_meeting_task to permanently remove resources in Meeting Automation MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a task is a destructive operation that cannot be undone—it permanently removes data from Asana. While the blast radius may be limited to a single task (reducing severity from critical to high), deletion qualifies as Destructive rather than Write (which implies reversible modifications). This is the most severe applicable category.
From the tool's definition Tool name 'delete_meeting_task' combined with description 'Delete an Asana task' explicitly indicates irreversible deletion of data.
Attacks that exploit this kind of access
Delete an Asana task. It is categorised as a Destructive tool in the Meeting Automation MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Meeting Automation MCP Server MCP server in PolicyLayer and add a rule for delete_meeting_task: 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 Meeting Automation MCP Server. Nothing to install.
delete_meeting_task 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_meeting_task 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_meeting_task. 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_meeting_task is provided by the Meeting Automation MCP Server MCP server (ramhori/meeting-automation-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 →