update_work_item_state · PingCode MCP Server MCP

WHAT IT DOES

What update_work_item_state does on PingCode MCP Server

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

WHY IT NEEDS A POLICY

Why update_work_item_state needs a policy

This tool modifies the state of work items in a project management system (bugs, requirements, tasks) in a reversible manner. State changes can typically be undone by changing to a previous state or reverting to prior values. This makes it a Write category tool rather than Execute (which would involve running arbitrary operations) or Destructive (which involves irreversible deletion).

From the tool's definition Tool name 'update_work_item_state' and description '更新工作项（缺陷/需求/任务）的状态' (Update work item [bug/requirement/task] state) indicates modification of existing project management data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_work_item_state Rate-limited

update_work_item_state 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": {
    "update_work_item_state": {
      "limits": [
        {
          "counter": "update_work_item_state_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 PingCode MCP Server, so you can run agents against it safely.

FAQ

Questions about update_work_item_state

What does the update_work_item_state tool do? +

更新工作项（缺陷/需求/任务）的状态。通过状态名称指定目标状态。. It is categorised as a Write tool in the PingCode 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 update_work_item_state? +

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

What risk level is update_work_item_state? +

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

Can I rate-limit update_work_item_state? +

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

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

update_work_item_state is provided by the PingCode MCP Server MCP server (ratatatat1/pingcode-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.