jira_create_issue
A write tool on the Integrations MCP server.
This record as markdown: /tools/shriram-vasudevan-integrations-mcp/jira-create-issue.md
What jira_create_issue does on Integrations MCP
AI agents use jira_create_issue to create or update resources in Integrations MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Integrations MCP environment.
Why jira_create_issue is rated Medium
Creating a Jira issue adds a new data record that can be modified or deleted later, making it a reversible Write operation rather than destructive. Severity is medium because misconfigured issue creation could spam workflows or disclose sensitive information in ticket descriptions, but the operation itself is not irreversible or financial.
From the tool's definition Tool name 'jira_create_issue' indicates creation of a new issue in Jira. The prefix 'create' is characteristic of Write operations that modify data reversibly.
Attacks that exploit this kind of access
The rule that runs jira_create_issue safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For jira_create_issue, this is the rule to start with:
jira_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 Integrations MCP, apply this rule, and every jira_create_issue call is checked against it from then on.
Questions about jira_create_issue
jira_create_issue is a write tool on the Integrations MCP server. It is categorised as a Write tool in the Integrations MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Integrations MCP server in PolicyLayer and add a rule for jira_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 Integrations MCP. Nothing to install.
jira_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 jira_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 jira_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.
jira_create_issue is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Integrations, and thousands of servers like it.
This server
Across the catalogue