gluecron_merge_pr
Merge an open PR. Enforces the same checks as the HTTP merge flow: not a draft, head SHA resolves, GateTest+AI-review hard gates pass, branch-protection rules satisfied. M3: soft-blocks when the pre-merge risk score is critical unless confirm_high_risk: true is passed. Returns {merged, sha?, reas...
This record as markdown: /tools/com-gluecron-gluecron/gluecron-merge-pr.md
What gluecron_merge_pr does on Gluecron
AI agents invoke gluecron_merge_pr to trigger actions in Gluecron. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
number | number | Yes | PR number |
confirm_high_risk | boolean | — | When true, bypass the M3 risk-score soft-block on critical-band PRs. |
Parameters from the server's own tool schema.
Why gluecron_merge_pr is rated High
Merging a PR triggers irreversible code integration into a branch with broad downstream effects.
From the tool's definition Merge an open PR... GateTest+AI-review hard gates pass... branch-protection rules satisfied
Attacks that exploit this kind of access
The rule that runs gluecron_merge_pr 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_merge_pr, this is the rule to start with:
gluecron_merge_pr stays usable, but rate-capped: a runaway agent can't fire it dozens of times 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_merge_pr call is checked against it from then on.
Questions about gluecron_merge_pr
Merge an open PR. Enforces the same checks as the HTTP merge flow: not a draft, head SHA resolves, GateTest+AI-review hard gates pass, branch-protection rules satisfied. M3: soft-blocks when the pre-merge risk score is critical unless confirm_high_risk: true is passed. Returns {merged, sha?, reason?, riskScore?}. It is categorised as a Execute tool in the Gluecron MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
gluecron_merge_pr accepts 4 parameters: repo, owner, number, confirm_high_risk. Required: 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_merge_pr: 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_merge_pr is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the gluecron_merge_pr 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_merge_pr. 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_merge_pr 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.
Across the catalogue