Delete a post template from a project
AI agents call dooray_delete_template 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.
This tool performs an irreversible deletion operation on a template resource. Once deleted, the template cannot be recovered through normal means, and any workflows or processes depending on that template may be disrupted. The blast radius depends on how widely the template is used within the project, but the destructive nature of the operation warrants a 'high' severity classification.
From the tool's definition Tool name is 'dooray_delete_template' and description states 'Delete a post template from a project' — the verb 'Delete' combined with 'from a project' indicates irreversible removal of data.
Attacks that exploit this kind of access
Delete a post template from a project. 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_delete_template: 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_delete_template 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_delete_template 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_delete_template. 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_delete_template is provided by the Dooray MCP Server MCP server (kwanok/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 →