Creates a new issue in Jira with the specified details.
AI agents use create_jira_issue to create or update resources in AWS_CloudGuardMCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AWS_CloudGuardMCP environment.
The tool creates new records (Jira issues) which is a reversible write operation. While it modifies state in an external system, Jira issues can be deleted or closed, making it Write rather than Destructive. Severity is medium because malicious creation of numerous tickets could degrade Jira workflows and alert fatigue, but the impact is organizational rather than involving data loss or financial harm.
From the tool's definition Tool name is 'create_jira_issue' and description states 'Creates a new issue in Jira with the specified details.' This directly creates new data in an external system (Jira).
Attacks that exploit this kind of access
Creates a new issue in Jira with the specified details. It is categorised as a Write tool in the AWS_CloudGuardMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AWS_CloudGuard MCP server in PolicyLayer and add a rule for create_jira_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 AWS_CloudGuardMCP. Nothing to install.
create_jira_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_jira_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_jira_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_jira_issue is provided by the AWS_CloudGuard MCP server (madhurprash/aws_cloudguardmcp). 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 →