sentry_action
Interact with the Sentry REST API: list projects and issues, get issue details and events, and resolve issues.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sentry-action.md
What sentry_action does on UnClick
AI agents call sentry_action to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Max number of results. |
query | string | — | Search query to filter issues. |
action | string | Yes | Action: list_projects, list_issues, get_issue, list_events, resolve_issue. |
cursor | string | — | Pagination cursor. |
issue_id | string | — | Issue ID (for get_issue, list_events, resolve_issue). |
auth_token | string | Yes | Sentry auth token. |
project_slug | string | — | Sentry project slug. |
stats_period | string | — | Time window for issue stats: 24h, 14d, etc. |
organization_slug | string | — | Sentry organization slug. |
Parameters from the server's own tool schema.
Why sentry_action is rated Low
Even though sentry_action only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs sentry_action safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sentry_action, this is the rule to start with:
sentry_action is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every sentry_action call is checked against it from then on.
Questions about sentry_action
Interact with the Sentry REST API: list projects and issues, get issue details and events, and resolve issues. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sentry_action accepts 9 parameters: limit, query, action, cursor, issue_id, auth_token, project_slug, stats_period, organization_slug. Required: action, auth_token. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sentry_action: 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 UnClick. Nothing to install.
sentry_action is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the sentry_action 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 sentry_action. 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.
sentry_action is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue