bugsnag_get_current_project

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/bugsnag-get-current-project.md

WHAT IT DOES

What bugsnag_get_current_project does on SmartBear MCP

AI agents call bugsnag_get_current_project 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.

RISK

Why bugsnag_get_current_project is rated Low

This tool queries configuration or state to determine a default project context for other tools. It performs no modifications, deletions, executions, or financial operations. It is a simple read operation that returns metadata about the current project configuration.

From the tool's definition Tool name is 'bugsnag_get_current_project' and description states 'Retrieve the current project' — a retrieval operation. Use case explicitly states 'Understand if a current project has been set', which is purely informational with no side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs bugsnag_get_current_project 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_get_current_project, this is the rule to start with:

bugsnag_get_current_project Allowed

bugsnag_get_current_project is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every bugsnag_get_current_project call is checked against it from then on.

FAQ

Questions about bugsnag_get_current_project

What does the bugsnag_get_current_project tool do? +

Retrieve the 'current' project on which tools should operate by default. This allows BugSnag tools to be called with no projectId parameter. Parameters: Use Cases: 1. Understand if a current project has been set Hints: 1. If a project is returned, it can be assumed that the user expects interactions with BugSnag tools to refer to this project 2. If this tool returns no current project then other BugSnag tools will require an explicit project ID parameter 3. Call the List Projects tool to see all projects that the user has access to. Get the project ID from this list either by asking the user for the project name or slug 4. You might find a BugSnag API key in the user's code where they configure the BugSnag SDK that can be matched to a project 'apiKey' field from the project list. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on bugsnag_get_current_project? +

Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_get_current_project: 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.

What risk level is bugsnag_get_current_project? +

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

Can I rate-limit bugsnag_get_current_project? +

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

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

bugsnag_get_current_project 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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →