gluecron_create_issue
Create a new issue on a Gluecron repository. Requires authenticated caller with write access on the target repo. Returns {number, url}.
This record as markdown: /tools/com-gluecron-gluecron/gluecron-create-issue.md
What gluecron_create_issue does on Gluecron
AI agents use gluecron_create_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 |
|---|---|---|---|
body | string | — | Issue body (Markdown). Optional. |
repo | string | Yes | Repo name |
owner | string | Yes | Repo owner username |
title | string | Yes | Issue title |
Parameters from the server's own tool schema.
Why gluecron_create_issue is rated Medium
Creating an issue is a reversible write operation that adds data to a repository. It requires write permissions and modifies the repository state, but the change can be undone (issues can be closed, deleted, or edited). This is less severe than Execute (which runs arbitrary code) or Destructive (which permanently removes data), and does not involve financial transactions.
From the tool's definition Tool description states 'Create a new issue' and 'Requires authenticated caller with write access on the target repo'. The return of {number, url} confirms creation of new data.
Risk signalsAccepts raw HTML/template content (body)
Attacks that exploit this kind of access
The rule that runs gluecron_create_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_create_issue, this is the rule to start with:
gluecron_create_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_create_issue call is checked against it from then on.
Questions about gluecron_create_issue
Create a new issue on a Gluecron repository. Requires authenticated caller with write access on the target repo. Returns {number, url}. 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_create_issue accepts 4 parameters: body, repo, owner, title. Required: repo, owner, title. 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_create_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_create_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_create_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_create_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_create_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