bulk_update_work_packages · Tonle OpenProject MCP Server MCP

WHAT IT DOES

What bulk_update_work_packages does on Tonle OpenProject MCP Server

AI agents use bulk_update_work_packages to create or update resources in Tonle OpenProject MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tonle OpenProject MCP Server environment.

WHY IT NEEDS A POLICY

Why bulk_update_work_packages needs a policy

This tool modifies data (work packages) reversibly through updates rather than deletion or financial transactions. It is categorized as Write rather than Execute because it performs a data modification operation, not arbitrary code/command execution.

From the tool's definition Tool name is 'bulk_update_work_packages' and description states 'Update multiple work packages in one call.' The verb 'update' indicates modification of existing data.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

bulk_update_work_packages Rate-limited

bulk_update_work_packages 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": {
    "bulk_update_work_packages": {
      "limits": [
        {
          "counter": "bulk_update_work_packages_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 Tonle OpenProject MCP Server, so you can run agents against it safely.

FAQ

Questions about bulk_update_work_packages

What does the bulk_update_work_packages tool do? +

Update multiple work packages in one call. Put shared changes in. It is categorised as a Write tool in the Tonle OpenProject MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on bulk_update_work_packages? +

Register the Tonle OpenProject MCP Server MCP server in PolicyLayer and add a rule for bulk_update_work_packages: 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 Tonle OpenProject MCP Server. Nothing to install.

What risk level is bulk_update_work_packages? +

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

Can I rate-limit bulk_update_work_packages? +

Yes. Add a rate_limit block to the bulk_update_work_packages 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 bulk_update_work_packages completely? +

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

bulk_update_work_packages is provided by the Tonle OpenProject MCP Server MCP server (liratanak/openproject-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.