get_sentry_issue

get_sentry_issue

Server Helm Chart CLI jeff-nasseri/servers
Category Read
Risk class Low
Parameters 00 required

What get_sentry_issue does on Helm Chart CLI

AI agents call get_sentry_issue to retrieve information from Helm Chart CLI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_sentry_issue needs a policy

The naming strongly suggests a data retrieval operation ('get') from Sentry. No modification, execution, or deletion is implied by the name. The tool would allow querying issue metadata, but not creating financial obligations or destructively modifying data.

From the tool's definition Tool name 'get_sentry_issue' indicates retrieval of issue data from Sentry (error tracking service). Description is empty, limiting confidence.

Questions about get_sentry_issue

What does the get_sentry_issue tool do? +

get_sentry_issue. It is categorised as a Read tool in the Helm Chart CLI MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_sentry_issue? +

Register the Helm Chart CLI MCP server in PolicyLayer and add a rule for get_sentry_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 Helm Chart CLI. Nothing to install.

What risk level is get_sentry_issue? +

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

Can I rate-limit get_sentry_issue? +

Yes. Add a rate_limit block to the get_sentry_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 get_sentry_issue completely? +

Set action: deny in the PolicyLayer policy for get_sentry_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 get_sentry_issue? +

get_sentry_issue is provided by the Helm Chart CLI MCP server (jeff-nasseri/servers). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.