Delete a project folder. Projects in the folder are not deleted.
AI agents call dida365_delete_folder to permanently remove resources in Dida365 Agent — 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. While the description clarifies that contained projects are not deleted, the folder itself and its organizational structure are permanently destroyed. This matches the Destructive category (delete, drop, purge actions that cannot be undone).
From the tool's definition 'Delete a project folder' — the tool irreversibly removes a folder object. Although projects within are preserved, the folder structure and its metadata are permanently deleted and cannot be undone.
Attacks that exploit this kind of access
Delete a project folder. Projects in the folder are not deleted. It is categorised as a Destructive tool in the Dida365 Agent MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Dida365 Agent MCP server in PolicyLayer and add a rule for dida365_delete_folder: 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 Dida365 Agent. Nothing to install.
dida365_delete_folder 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 dida365_delete_folder 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 dida365_delete_folder. 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.
dida365_delete_folder is provided by the Dida365 Agent MCP server (linhai0872/dida365-agent). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
dida365_delete_folder is one line of Dida365 Agent's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →