Submit a review for a pull request.
AI agents use update_reviews 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 creates or modifies review records on pull requests, which is a reversible write operation. While reviews can influence code merging decisions, the action itself is not destructive (reviews can be updated or dismissed) and does not directly move money or execute arbitrary code.
From the tool's definition Tool name 'update_reviews' and description 'Submit a review for a pull request' indicate creation/modification of review data on a pull request.
Attacks that exploit this kind of access
Submit a review for 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 update_reviews: 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.
update_reviews 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 update_reviews 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 update_reviews. 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.
update_reviews 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 →