Creates an issue to the users
AI agents use create_issue to create or update resources in Jira Issue MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Jira Issue MCP Server environment.
This tool creates new Jira issues, which is a reversible write operation. It modifies the Jira system by adding new data but does not delete, execute arbitrary code, or move money. Severity is medium because unauthorized issue creation could lead to data pollution, project disruption, or spam, but the blast radius is limited compared to destructive or financial operations.
From the tool's definition Tool name 'create_issue' combined with description 'Creates an issue to the users' clearly indicates data creation. Server description confirms 'create and manage issues directly from MCP-compatible clients.'
Attacks that exploit this kind of access
Creates an issue to the users. It is categorised as a Write tool in the Jira Issue MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Jira Issue MCP Server MCP server in PolicyLayer and add a rule for 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 Jira Issue MCP Server. Nothing to install.
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 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 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.
create_issue is provided by the Jira Issue MCP Server MCP server (razvancanuci/jira-issue-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →