issue-update · Python MCP: Risk & Policy

WHAT IT DOES

What issue-update does on Python

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

WHY IT NEEDS A POLICY

Why issue-update needs a policy

This tool creates or modifies issue data (title, body, labels, assignees, milestone, projects) in a reversible manner. While it changes existing records, these changes are not destructive—metadata can be edited or reverted.

From the tool's definition Updates issue metadata (title, body, labels, assignees, milestone, projects) — modifies data reversibly without deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

issue-update Rate-limited

issue-update 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": {
    "issue-update": {
      "limits": [
        {
          "counter": "issue-update_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 Python, so you can run agents against it safely.

FAQ

Questions about issue-update

What does the issue-update tool do? +

Updates issue metadata (title, body, labels, assignees, milestone, projects). It is categorised as a Write tool in the Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on issue-update? +

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

What risk level is issue-update? +

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

Can I rate-limit issue-update? +

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

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

issue-update is provided by the Python MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

issue-update is one line of Python's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →