Create a Jira ticket from a Sentry issue and link them together
AI agents use create_jira_ticket to create or update resources in Sentry Investigator — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sentry Investigator environment.
This tool creates new Jira tickets, which is a reversible write operation—tickets can be deleted or modified later. It does not execute arbitrary code, delete data, move money, or trigger destructive operations.
From the tool's definition Tool description states 'Create a Jira ticket from a Sentry issue and link them together'. The word 'Create' indicates it generates new data in the Jira system, which is a write operation that creates but does not destroy or modify existing data irreversibly.
Attacks that exploit this kind of access
Create a Jira ticket from a Sentry issue and link them together. It is categorised as a Write tool in the Sentry Investigator MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sentry Investigator MCP server in PolicyLayer and add a rule for create_jira_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 Sentry Investigator. Nothing to install.
create_jira_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_jira_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_jira_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_jira_ticket is provided by the Sentry Investigator MCP server (vibe-code-agent/sentry-mcp). 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 →