Create a kanban column. Move tasks into it via update_task's columnId.
AI agents use dida365_create_column to create or update resources in Dida365 Agent — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Dida365 Agent environment.
This tool creates (writes) a new kanban column, which is a reversible operation—columns can be deleted or modified later. It does not execute arbitrary commands, delete data irreversibly, or involve financial transactions. Low severity because miscreating columns has minimal blast radius in a task management context (users can reorganize or remove them).
From the tool's definition Tool creates a kanban column (reversible data creation). Description states 'Create a kanban column' which is an explicit write operation.
Attacks that exploit this kind of access
Create a kanban column. Move tasks into it via update_task's columnId. It is categorised as a Write tool in the Dida365 Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Dida365 Agent MCP server in PolicyLayer and add a rule for dida365_create_column: 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_create_column is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the dida365_create_column 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_create_column. 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_create_column 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.
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 →