gluecron_label_issue
Attach one or more labels to an issue. Labels are created if they don't yet exist on the repo. Requires 'repo' scope. Returns {labels}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-label-issue.md
What gluecron_label_issue does on Gluecron
AI agents use gluecron_label_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 | |
owner | string | Yes | |
labels | array | Yes | Label names (strings) |
number | number | Yes |
Parameters from the server's own tool schema.
Why gluecron_label_issue is rated Medium
This tool modifies issue metadata by attaching labels and potentially creating new labels in the repository. This is a write operation that changes repository state reversibly (labels can be removed or modified later). It does not delete data, execute arbitrary code, or move money, so it is Write rather than a more severe category.
From the tool's definition Attach one or more labels to an issue. Labels are created if they don't yet exist on the repo.
Attacks that exploit this kind of access
The rule that runs gluecron_label_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_label_issue, this is the rule to start with:
gluecron_label_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_label_issue call is checked against it from then on.
Questions about gluecron_label_issue
Attach one or more labels to an issue. Labels are created if they don't yet exist on the repo. Requires 'repo' scope. Returns {labels}. 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_label_issue accepts 4 parameters: repo, owner, labels, number. Required: repo, owner, labels, 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_label_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_label_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_label_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_label_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_label_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