Capture a CDP performance trace and return named insights
AI agents invoke oc_performance_insights to trigger actions in OpenChrome. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes a Chrome DevTools Protocol (CDP) performance trace in the browser. While it primarily reads/returns data (insights), it actively triggers an instrumentation session in the browser runtime — an external operation with side effects on the browser process. It falls under Execute rather than Read because it initiates an active tracing operation via CDP rather than passively querying existing state.
From the tool's definition Capture a CDP performance trace and return named insights
Documented attack patterns abuse exactly the kind of access oc_performance_insights gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OpenChrome, and nothing reaches the server without passing your rules. This is the rule we recommend for oc_performance_insights:
{
"version": "1",
"default": "deny",
"tools": {
"oc_performance_insights": {
"limits": [
{
"counter": "oc_performance_insights_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}oc_performance_insights stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Capture a CDP performance trace and return named insights. It is categorised as a Execute tool in the OpenChrome MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the OpenChrome MCP server in PolicyLayer and add a rule for oc_performance_insights: 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 OpenChrome. Nothing to install.
oc_performance_insights is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the oc_performance_insights 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 oc_performance_insights. 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.
oc_performance_insights is provided by the OpenChrome MCP server (shaun0927/openchrome). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 106 OpenChrome tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
106 OpenChrome tools catalogued and risk-classified — across an index of 42,500+ MCP servers.