gluecron_assign_issue
Assign an issue to a user. Gluecron does not yet have a dedicated assignee table; assignment is modelled as an assignee:<username> label so it integrates with existing label tooling. Requires 'repo' scope.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-assign-issue.md
What gluecron_assign_issue does on Gluecron
AI agents use gluecron_assign_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 | |
number | number | Yes | |
assignee | string | Yes | Username to assign |
Parameters from the server's own tool schema.
Why gluecron_assign_issue is rated Medium
This tool creates or modifies data (issue labels/assignments) without permanent destruction or external code execution. The blast radius is medium because mis-assignment could misdirect work or notify unintended users, but the change is easily reversible. It requires 'repo' scope, limiting but not eliminating risk.
From the tool's definition The tool 'assigns an issue to a user' by adding an 'assignee:<username>' label. This modifies issue metadata reversibly—the assignment can be changed or removed later.
Attacks that exploit this kind of access
The rule that runs gluecron_assign_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_assign_issue, this is the rule to start with:
gluecron_assign_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_assign_issue call is checked against it from then on.
Questions about gluecron_assign_issue
Assign an issue to a user. Gluecron does not yet have a dedicated assignee table; assignment is modelled as an assignee:<username> label so it integrates with existing label tooling. 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_assign_issue accepts 4 parameters: repo, owner, number, assignee. Required: repo, owner, number, assignee. 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_assign_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_assign_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_assign_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_assign_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_assign_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