create_jira_from_sentry · Sentry Investigator MCP

WHAT IT DOES

What create_jira_from_sentry does on Sentry Investigator

AI agents use create_jira_from_sentry 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.

WHY IT NEEDS A POLICY

Why create_jira_from_sentry needs a policy

This tool creates new data (Jira tickets) in an external system based on Sentry issues. While the creation is reversible (tickets can be deleted), the tool modifies state by introducing new work items into a project management system. This is a Write operation rather than Read (it creates, not just retrieves), not Execute (it doesn't run arbitrary code or commands), and not Destructive (creation is reversible).

From the tool's definition Tool description states 'Create a Jira ticket directly from a Sentry issue' — the verb 'create' indicates data creation. This is a write operation that generates new records (Jira tickets) with side effects that are reversible (tickets can be deleted).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_jira_from_sentry Rate-limited

create_jira_from_sentry 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_jira_from_sentry": {
      "limits": [
        {
          "counter": "create_jira_from_sentry_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Sentry Investigator, so you can run agents against it safely.

FAQ

Questions about create_jira_from_sentry

What does the create_jira_from_sentry tool do? +

Create a Jira ticket directly from a Sentry issue with automatic linking and rich context. 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.

How do I enforce a policy on create_jira_from_sentry? +

Register the Sentry Investigator MCP server in PolicyLayer and add a rule for create_jira_from_sentry: 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.

What risk level is create_jira_from_sentry? +

create_jira_from_sentry is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit create_jira_from_sentry? +

Yes. Add a rate_limit block to the create_jira_from_sentry 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.

How do I block create_jira_from_sentry completely? +

Set action: deny in the PolicyLayer policy for create_jira_from_sentry. 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.

What MCP server provides create_jira_from_sentry? +

create_jira_from_sentry 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.