dida365_batch_complete_tasks · Dida365 Agent MCP

WHAT IT DOES

What dida365_batch_complete_tasks does on Dida365 Agent

AI agents use dida365_batch_complete_tasks 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_batch_complete_tasks needs a policy

This tool modifies task data by changing their completion status, which is a reversible write operation. While the change itself is permanent in state, the task record can theoretically be marked incomplete again (undo capability common in task management systems). It affects multiple records but does not delete data, so it falls under Write rather than Destructive.

From the tool's definition Tool name 'dida365_batch_complete_tasks' and description 'Mark multiple tasks in a project as completed' indicate state modification of task records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dida365_batch_complete_tasks Rate-limited

dida365_batch_complete_tasks 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_batch_complete_tasks": {
      "limits": [
        {
          "counter": "dida365_batch_complete_tasks_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_batch_complete_tasks

What does the dida365_batch_complete_tasks tool do? +

Mark multiple tasks in a project as completed. 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_batch_complete_tasks? +

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

What risk level is dida365_batch_complete_tasks? +

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

Can I rate-limit dida365_batch_complete_tasks? +

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

How do I block dida365_batch_complete_tasks completely? +

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

What MCP server provides dida365_batch_complete_tasks? +

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