update_pr_description · Downscoping MCP: Risk & Policy

WHAT IT DOES

What update_pr_description does on Downscoping

AI agents use update_pr_description 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_pr_description needs a policy

This tool modifies pull request metadata (title and description) but does not delete, destroy, or execute code. The changes are reversible—descriptions can be edited again or reverted. While it could be misused to mislead reviewers or obstruct transparency in CI/CD pipelines, the blast radius is limited to metadata changes rather than code execution or data destruction.

From the tool's definition Tool name 'update_pr_description' and description 'Update the title and description of a pull request' indicate modification of existing pull request metadata. The word 'Update' confirms reversible data modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_pr_description Rate-limited

update_pr_description 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_pr_description": {
      "limits": [
        {
          "counter": "update_pr_description_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_pr_description

What does the update_pr_description tool do? +

Update the title and description of a 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_pr_description? +

Register the Downscoping MCP server in PolicyLayer and add a rule for update_pr_description: 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_pr_description? +

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

Can I rate-limit update_pr_description? +

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

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

update_pr_description 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.