update_assignees · Downscoping MCP: Risk & Policy

WHAT IT DOES

What update_assignees does on Downscoping

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

WHY IT NEEDS A POLICY

Why update_assignees needs a policy

This tool creates or modifies data reversibly by changing assignee metadata on issues or PRs. It is not destructive (assignees can be changed again), not financial, and not a read operation. While it modifies GitHub state, the blast radius is limited to reassigning work tasks rather than deleting data or executing arbitrary code.

From the tool's definition Tool name 'update_assignees' and description 'Update assignees for an issue or pull request' indicate modification of metadata on existing GitHub resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_assignees Rate-limited

update_assignees 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_assignees": {
      "limits": [
        {
          "counter": "update_assignees_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 Downscoping, so you can run agents against it safely.

FAQ

Questions about update_assignees

What does the update_assignees tool do? +

Update assignees for an issue or pull request. It is categorised as a Write tool in the Downscoping 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_assignees? +

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

What risk level is update_assignees? +

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

Can I rate-limit update_assignees? +

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

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

update_assignees is provided by the Downscoping MCP server (kbroughton/downscoping-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.