sentry_get_issue

Get details of a specific Sentry issue by ID.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/sentry-get-issue.md

WHAT IT DOES

What sentry_get_issue does on Integrations MCP

AI agents call sentry_get_issue to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sentry_get_issue is rated Low

The tool retrieves and queries error tracking data from Sentry by issue ID. This is a read-only operation that returns information about bugs/errors without creating, modifying, deleting, or executing anything. No reversible or irreversible changes occur, and no external operations are triggered beyond data lookup.

From the tool's definition Tool name 'sentry_get_issue' combined with description 'Get details of a specific Sentry issue by ID' indicates retrieval of issue metadata without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sentry_get_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 sentry_get_issue, this is the rule to start with:

sentry_get_issue Allowed

sentry_get_issue is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sentry_get_issue": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every sentry_get_issue call is checked against it from then on.

FAQ

Questions about sentry_get_issue

What does the sentry_get_issue tool do? +

Get details of a specific Sentry issue by ID. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sentry_get_issue? +

Register the Integrations MCP server in PolicyLayer and add a rule for sentry_get_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.

What risk level is sentry_get_issue? +

sentry_get_issue is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sentry_get_issue? +

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

How do I block sentry_get_issue completely? +

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

What MCP server provides sentry_get_issue? +

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

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →