list_issues

THE RISK

Low Risk

Why list_issues needs a policy

This tool retrieves and queries error tracking data without creating, modifying, deleting, or executing anything. It is a passive read operation that returns information about grouped error occurrences. The blast radius of misuse is minimal—an attacker could only observe existing error data, not modify systems or access financial information.

From the tool's definition Tool name 'list_issues' and description 'List issues for a specific project' indicate a retrieval operation with no side effects. The server description confirms the tool 'supports listing projects, teams, issues' as a query capability.

Documented attack patterns abuse exactly the kind of access list_issues gives an agent:

POLICY

How to control list_issues

PolicyLayer is an MCP gateway — it sits between your AI agents and Bugsink MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_issues:

policy.json

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

list_issues is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Bugsink MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Bugsink MCP Server tools

Write create_project Create a new project in a team Write create_release Create a new release for a project Write create_team Create a new team Write update_project Update an existing project Write update_team Update an existing team Read get_event Get detailed information about a specific event, including full stacktrace and context Read get_issue Get detailed information about a specific issue Read get_project Get detailed information about a specific project including DSN

All 16 Bugsink MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about list_issues

What does the list_issues tool do? +

List issues for a specific project. Issues represent grouped error occurrences. It is categorised as a Read tool in the Bugsink MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_issues? +

Register the Bugsink MCP Server MCP server in PolicyLayer and add a rule for list_issues: 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 Bugsink MCP Server. Nothing to install.

What risk level is list_issues? +

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

Can I rate-limit list_issues? +

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

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

list_issues is provided by the Bugsink MCP Server MCP server (j-shelfwood/bugsink-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Bugsink MCP Server tool call.

Start from Bugsink MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →