Add an inline review comment to a file line within a pull request.
AI agents use add_inline_pr_comment 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.
This tool writes comment data to a pull request, which is reversible (comments can be edited or deleted). It does not delete data (Destructive), execute arbitrary code (Execute), trigger financial operations (Financial), or merely read data (Read). The severity is medium because misuse could spam pull requests with unwanted comments, but the blast radius is limited to a single repository and is easily remediated.
From the tool's definition add_inline_pr_comment creates new comment data within a pull request, modifying the PR's review state. The word 'Add' indicates creation of new content.
Attacks that exploit this kind of access
Add an inline review comment to a file line within 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.
Register the Downscoping MCP server in PolicyLayer and add a rule for add_inline_pr_comment: 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.
add_inline_pr_comment is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the add_inline_pr_comment 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.
Set action: deny in the PolicyLayer policy for add_inline_pr_comment. 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.
add_inline_pr_comment 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →