bugsnag_list_projects
List all projects in the organization that the current user has access to, or find a project matching an API key. Parameters: - apiKey (string): The API key of the BugSnag project, if known. Use Cases: 1. Get an overview of all projects in the organization 2. Locate a project by its API key if kn...
This record as markdown: /tools/smartbear-mcp/bugsnag-list-projects.md
What bugsnag_list_projects does on SmartBear MCP
AI agents call bugsnag_list_projects to retrieve information from SmartBear MCP 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 |
|---|---|---|---|
apiKey | string | — | The API key of the BugSnag project, if known. |
Parameters from the server's own tool schema.
Why bugsnag_list_projects is rated Low
This is a query/retrieval operation with no side effects. It gathers organizational data for informational purposes. The API key parameter is used for filtering results, not for executing operations. Blast radius is minimal—disclosure of project names and metadata poses low risk in a properly configured system where users should already know their own projects.
From the tool's definition Tool "lists all projects" and "locate a project"; returns metadata about projects accessible to the user without modifying or executing anything. The description explicitly states it retrieves project information.
Risk signalsHandles credentials or secrets (apiKey)
Attacks that exploit this kind of access
The rule that runs bugsnag_list_projects safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bugsnag_list_projects, this is the rule to start with:
bugsnag_list_projects 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 SmartBear MCP, apply this rule, and every bugsnag_list_projects call is checked against it from then on.
Questions about bugsnag_list_projects
List all projects in the organization that the current user has access to, or find a project matching an API key. Parameters: - apiKey (string): The API key of the BugSnag project, if known. Use Cases: 1. Get an overview of all projects in the organization 2. Locate a project by its API key if known from the user's code Hints: 1. Project IDs from this list can be used with other tools when no project API key is configured. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
bugsnag_list_projects accepts 1 parameter: apiKey. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_list_projects: 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 SmartBear MCP. Nothing to install.
bugsnag_list_projects 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 bugsnag_list_projects 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 bugsnag_list_projects. 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.
bugsnag_list_projects is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue