AI agents call list_teams to retrieve information from Bugsink MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves team information from the error tracking system without creating, modifying, or deleting any data. It is a read-only query operation that simply enumerates existing teams. The blast radius of misuse is minimal, as it only exposes organizational structure metadata that may already be visible to authenticated users.
From the tool's definition Tool name is 'list_teams' and description states 'List all teams in the Bugsink instance' — a pure retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access list_teams gives an agent:
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_teams:
{
"version": "1",
"default": "deny",
"tools": {
"list_teams": {}
}
}list_teams is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all teams in the Bugsink instance. It is categorised as a Read tool in the Bugsink MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Bugsink MCP Server MCP server in PolicyLayer and add a rule for list_teams: 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.
list_teams 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 list_teams 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 list_teams. 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.
list_teams 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.
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.
Free to start. No card required.
16 Bugsink MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.