bugsnag_list_trace_fields

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-trace-fields.md

WHAT IT DOES

What bugsnag_list_trace_fields does on SmartBear MCP

AI agents call bugsnag_list_trace_fields 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_trace_fields is rated Low

This tool queries and returns metadata about available trace fields without side effects. It retrieves schema/attribute information to enable filtering elsewhere, which is a pure read operation with minimal blast radius if misused by an agent.

From the tool's definition Tool name includes 'list', description states 'Get available trace fields/attributes for filtering'. The use cases confirm retrieval only: 'Find available custom attributes', 'Understand what metadata is attached', 'Build dynamic filters'.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

bugsnag_list_trace_fields Allowed

bugsnag_list_trace_fields 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_trace_fields": {}
  }
}

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

FAQ

Questions about bugsnag_list_trace_fields

What does the bugsnag_list_trace_fields tool do? +

Get available trace fields/attributes for filtering 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. Find available custom attributes for performance filtering 2. Understand what metadata is attached to traces 3. Build dynamic filters based on available fields Examples: 1. Get all trace fields json {} Expected Output: Array of field names and types available for filtering Hints: 1. Trace fields are custom attributes added to spans 2. Use these fields for filtering other performance queries. 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_trace_fields accept? +

bugsnag_list_trace_fields 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_trace_fields? +

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

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

Can I rate-limit bugsnag_list_trace_fields? +

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

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

bugsnag_list_trace_fields 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 → The MCP Attack Database →

Guides

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