bugsnag_list_project_event_filters

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/bugsnag-list-project-event-filters.md

WHAT IT DOES

What bugsnag_list_project_event_filters does on SmartBear MCP

AI agents call bugsnag_list_project_event_filters 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
`projectId`	string	—	Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools.

Parameters from the server's own tool schema.

RISK

Why bugsnag_list_project_event_filters is rated Low

This tool retrieves metadata about available filter fields without modifying, executing, or deleting anything. It is purely informational, helping users understand the schema of filterable fields before constructing queries. The single optional parameter (projectId) only affects scope, not the nature of the operation. This is a standard Read operation with minimal risk.

From the tool's definition Tool description states 'Get available event filter fields for a project' and use cases describe discovering and finding field names for filtering—all read-only discovery operations. No parameter accepts dynamic query values that would trigger side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bugsnag_list_project_event_filters Allowed

bugsnag_list_project_event_filters 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_list_project_event_filters": {}
  }
}

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_list_project_event_filters call is checked against it from then on.

FAQ

Questions about bugsnag_list_project_event_filters

What does the bugsnag_list_project_event_filters tool do? +

Get available event filter fields for a project Parameters: - projectId (string): Unique identifier of the project. This is optional if a current project is set and is used to set the current project for BugSnag tools. Use Cases: 1. Discover what filter fields are available before searching for errors 2. Find the correct field names for filtering by user, environment, or custom metadata 3. Understand filter options and data types for building complex queries Examples: 1. Get all available filter fields json {} Expected Output: JSON array of EventField objects containing display_id, custom flag, and filter/pivot options Hints: 1. Use this tool before the List Errors or Get Error tools to understand available filters 2. Look for display_id field in the response - these are the field names to use in filters. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does bugsnag_list_project_event_filters accept? +

bugsnag_list_project_event_filters accepts 1 parameter: projectId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on bugsnag_list_project_event_filters? +

Register the SmartBear MCP server in PolicyLayer and add a rule for bugsnag_list_project_event_filters: 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_list_project_event_filters? +

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

Can I rate-limit bugsnag_list_project_event_filters? +

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

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

bugsnag_list_project_event_filters 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server →get_event_details on CTFtime MCP Server → The MCP Attack Database →

Guides

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