gluecron_request_changes
Post a 'changes requested' AI-review comment on a PR. The comment is tagged with isAiReview=true so the gate-checker recognises it. Requires 'repo' scope.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-request-changes.md
What gluecron_request_changes does on Gluecron
AI agents use gluecron_request_changes to create or update resources in Gluecron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Gluecron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
body | string | Yes | Review body (Markdown) |
repo | string | Yes | |
owner | string | Yes | |
number | number | Yes |
Parameters from the server's own tool schema.
Why gluecron_request_changes is rated Medium
This tool creates a new review comment on a pull request, which is a reversible modification of PR state. While it can influence code review gates and potentially block merges, it does not execute code, delete data, or move money. The impact is bounded to PR metadata/comments and depends on human review of the AI's judgment; therefore it is Write rather than Execute.
From the tool's definition Tool 'posts' a comment on a PR; description states 'Post a changes requested AI-review comment' which is a write operation that creates new data (a review comment) on the PR.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs gluecron_request_changes safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gluecron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For gluecron_request_changes, this is the rule to start with:
gluecron_request_changes 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Gluecron, apply this rule, and every gluecron_request_changes call is checked against it from then on.
Questions about gluecron_request_changes
Post a 'changes requested' AI-review comment on a PR. The comment is tagged with isAiReview=true so the gate-checker recognises it. Requires 'repo' scope. It is categorised as a Write tool in the Gluecron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
gluecron_request_changes accepts 4 parameters: body, repo, owner, number. Required: body, repo, owner, number. The full parameter table on this page comes from the server's own tool schema.
Register the Gluecron MCP server in PolicyLayer and add a rule for gluecron_request_changes: 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 Gluecron. Nothing to install.
gluecron_request_changes 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 gluecron_request_changes 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 gluecron_request_changes. 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.
gluecron_request_changes is provided by the Gluecron MCP server (https://gluecron.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gluecron, and thousands of servers like it.
This server
Across the catalogue