AI agents call trace_viewer to retrieve information from Browser-Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name 'trace_viewer' suggests reading/viewing trace data (e.g., browser performance traces), which is a read operation. Given the server's focus on browser debugging and performance analysis, this likely retrieves and displays trace information without side effects. However, the empty description significantly lowers confidence.
From the tool's definition Tool name 'trace_viewer' and server context involving performance analysis and debugging in Chromium browsers. Description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access trace_viewer gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Browser-Debugger, and nothing reaches the server without passing your rules. This is the rule we recommend for trace_viewer:
{
"version": "1",
"default": "deny",
"tools": {
"trace_viewer": {}
}
}trace_viewer 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.
trace_viewer. It is categorised as a Read tool in the Browser-Debugger MCP Server, which means it retrieves data without modifying state.
Register the Browser-Debugger MCP server in PolicyLayer and add a rule for trace_viewer: 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 Browser-Debugger. Nothing to install.
trace_viewer 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 trace_viewer 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 trace_viewer. 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.
trace_viewer is provided by the Browser-Debugger MCP server (selvadinesh-giga/mcp-based-browser-debug-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Browser-Debugger, 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.
14 Browser-Debugger tools catalogued and risk-classified — across an index of 43,000+ MCP servers.