dida365_move_task · Dida365 Agent MCP: Risk & Policy

WHAT IT DOES

What dida365_move_task does on Dida365 Agent

AI agents use dida365_move_task 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.

WHY IT NEEDS A POLICY

Why dida365_move_task needs a policy

Moving a task between projects is a Write operation as it modifies task metadata reversibly without permanently deleting data or executing external code. The severity is medium because misuse could reorganize a user's task structure in unexpected ways, but the action can be undone by moving the task back to its original project.

From the tool's definition The tool name and description indicate it 'Move a task between projects,' which modifies the state of an existing task by changing its project association. This is a reversible data modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dida365_move_task Rate-limited

dida365_move_task stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "dida365_move_task": {
      "limits": [
        {
          "counter": "dida365_move_task_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Dida365 Agent, so you can run agents against it safely.

FAQ

Questions about dida365_move_task

What does the dida365_move_task tool do? +

Move a task between projects. 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.

How do I enforce a policy on dida365_move_task? +

Register the Dida365 Agent MCP server in PolicyLayer and add a rule for dida365_move_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 Dida365 Agent. Nothing to install.

What risk level is dida365_move_task? +

dida365_move_task is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit dida365_move_task? +

Yes. Add a rate_limit block to the dida365_move_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.

How do I block dida365_move_task completely? +

Set action: deny in the PolicyLayer policy for dida365_move_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.

What MCP server provides dida365_move_task? +

dida365_move_task 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.