update_project_item_status · GitHub Project MCP Server MCP

WHAT IT DOES

What update_project_item_status does on GitHub Project MCP Server

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

WHY IT NEEDS A POLICY

Why update_project_item_status needs a policy

This tool modifies project management metadata (item status) but does not delete data, execute arbitrary code, or trigger financial transactions. The change is reversible—a status can be updated back to a previous value.

From the tool's definition Tool updates the status field of a project item (e.g., Todo, In Progress, Done), which modifies existing project data reversibly. The description explicitly states 'Update the status', and status values are workflow states that can be changed back.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_project_item_status Rate-limited

update_project_item_status 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_project_item_status": {
      "limits": [
        {
          "counter": "update_project_item_status_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 GitHub Project MCP Server, so you can run agents against it safely.

FAQ

Questions about update_project_item_status

What does the update_project_item_status tool do? +

Update the status of a project item (e.g., Todo, In Progress, Done). It is categorised as a Write tool in the GitHub Project 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_project_item_status? +

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

What risk level is update_project_item_status? +

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

Can I rate-limit update_project_item_status? +

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

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

update_project_item_status is provided by the GitHub Project MCP Server MCP server (jaqarx/github-project-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.