AI agents use gitlab_create_issue to create or update resources in autoMate — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your autoMate environment.
Creating issues in GitLab is a reversible write operation that modifies project state by adding new issues. This could be misused by an AI agent to spam, create false reports, or pollute a project's issue tracker, but can be undone. The severity is high due to potential reputational damage and workflow disruption, though not critical since issues can be deleted.
From the tool's definition Tool name 'gitlab_create_issue' indicates creation of a GitLab issue. Description is empty, but the function name clearly denotes a write operation that creates a new artifact in GitLab.
Documented attack patterns abuse exactly the kind of access gitlab_create_issue gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and autoMate, and nothing reaches the server without passing your rules. This is the rule we recommend for gitlab_create_issue:
{
"version": "1",
"default": "deny",
"tools": {
"gitlab_create_issue": {
"limits": [
{
"counter": "gitlab_create_issue_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}gitlab_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.
Free to start. No card required.
gitlab_create_issue. It is categorised as a Write tool in the autoMate MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the autoMate MCP server in PolicyLayer and add a rule for gitlab_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 autoMate. Nothing to install.
gitlab_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 gitlab_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 gitlab_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.
gitlab_create_issue is provided by the autoMate MCP server (yuruotong1/automate). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 128 autoMate tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
128 autoMate tools catalogued and risk-classified — across an index of 42,500+ MCP servers.