Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field.
AI agents use create_ticket to create or update resources in Jira MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira MCP Server environment.
Creating a ticket is a write operation that creates new data in Jira. The severity is medium because while ticket creation is reversible (via delete_ticket), it can create noise, spam, or clutter in the Jira system if misused by an AI agent. The blast radius is limited compared to destructive or financial operations, but higher than simple read operations.
From the tool's definition Tool description states it 'Create a ticket on Jira on the api /rest/api/3/issue', which creates new data in Jira. This is a reversible operation (tickets can be deleted), not destructive.
Documented attack patterns abuse exactly the kind of access create_ticket gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Jira MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_ticket:
{
"version": "1",
"default": "deny",
"tools": {
"create_ticket": {
"limits": [
{
"counter": "create_ticket_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_ticket 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.
Create a ticket on Jira on the api /rest/api/3/issue. Do not use markdown in any field. It is categorised as a Write tool in the Jira MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira MCP Server MCP server in PolicyLayer and add a rule for create_ticket: 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 Jira MCP Server. Nothing to install.
create_ticket 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 create_ticket 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 create_ticket. 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.
create_ticket is provided by the Jira MCP Server MCP server (ks-gen-ai/jira-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Jira MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
11 Jira MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.