Manage Dooray tasks - list, get details, create, update, delete, change status, assign members
AI agents call dooray_tasks to permanently remove resources in Dooray MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
While this tool spans multiple categories (Read for list/get, Write for create/update, Execute for status/assign changes), the explicit inclusion of 'delete' makes it Destructive—the most severe category. Deleting tasks cannot be undone and represents irreversible data loss.
From the tool's definition Tool description explicitly includes 'delete' as a capability: 'Manage Dooray tasks - list, get details, create, update, delete, change status, assign members'. The 'delete' function irreversibly removes task data.
Attacks that exploit this kind of access
Manage Dooray tasks - list, get details, create, update, delete, change status, assign members. It is categorised as a Destructive tool in the Dooray MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dooray MCP Server MCP server in PolicyLayer and add a rule for dooray_tasks: 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 Dooray MCP Server. Nothing to install.
dooray_tasks 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 dooray_tasks 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 dooray_tasks. 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.
dooray_tasks is provided by the Dooray MCP Server MCP server (tallpizza/dooray-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 →