gluecron_close_pr
Close an open pull request without merging. Requires authenticated caller with write access. Idempotent. Returns {state}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-close-pr.md
What gluecron_close_pr does on Gluecron
AI agents use gluecron_close_pr 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 |
|---|---|---|---|
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
number | number | Yes | PR number |
Parameters from the server's own tool schema.
Why gluecron_close_pr is rated Medium
The tool modifies repository state by closing a PR, which is a reversible write operation. While PRs can be reopened, closing one changes project workflow state and blocks merge paths. The action requires write access, indicating it's a state-modifying operation rather than a read. It is not destructive (data remains intact, reversible), not financial, and not arbitrary code execution.
From the tool's definition Close an open pull request without merging. Requires authenticated caller with write access. Idempotent. Returns {state}.
Attacks that exploit this kind of access
The rule that runs gluecron_close_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_close_pr, this is the rule to start with:
gluecron_close_pr 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_close_pr call is checked against it from then on.
Questions about gluecron_close_pr
Close an open pull request without merging. Requires authenticated caller with write access. Idempotent. Returns {state}. 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_close_pr accepts 3 parameters: repo, owner, number. 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_close_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_close_pr 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_close_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_close_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_close_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.
This server
Across the catalogue