gluecron_unlabel_issue
Detach a label from an issue. Idempotent. Requires 'repo' scope. Returns {removed: boolean}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-unlabel-issue.md
What gluecron_unlabel_issue does on Gluecron
AI agents use gluecron_unlabel_issue 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 | |
label | string | Yes | |
owner | string | Yes | |
number | number | Yes |
Parameters from the server's own tool schema.
Why gluecron_unlabel_issue is rated Medium
Unlabeling is a Write operation: it modifies repository state (issue labels) reversibly and poses minimal blast radius. An agent removing labels cannot damage data or escalate privileges significantly. Unlike Destructive actions (which cannot be undone), label removal can be reversed by re-labeling. Severity is low because label changes have narrow scope and no financial, security, or data-loss implications.
From the tool's definition 'Detach a label from an issue' — modifies issue metadata by removing a label, a reversible state change. The response {removed: boolean} confirms the operation targets issue properties.
Attacks that exploit this kind of access
The rule that runs gluecron_unlabel_issue 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_unlabel_issue, this is the rule to start with:
gluecron_unlabel_issue 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_unlabel_issue call is checked against it from then on.
Questions about gluecron_unlabel_issue
Detach a label from an issue. Idempotent. Requires 'repo' scope. Returns {removed: boolean}. 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_unlabel_issue accepts 4 parameters: repo, label, owner, number. Required: repo, label, 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_unlabel_issue: 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_unlabel_issue 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_unlabel_issue 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_unlabel_issue. 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_unlabel_issue 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