AI agents invoke on_cdp_event to trigger actions in DrissionPageMCP. 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 sets up Chrome DevTools Protocol (CDP) event listeners and triggers CDP domain activation commands. It executes browser-level protocol commands that interact with the browser's internal APIs. While primarily a monitoring/setup action, it executes CDP commands with side effects (activating domains, registering event handlers), placing it in Execute rather than Read.
From the tool's definition 设置监听CDP事件 (Set up listening for CDP events); requires running CDP commands to activate domains like 'Network.enable'
Documented attack patterns abuse exactly the kind of access on_cdp_event gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for on_cdp_event:
{
"version": "1",
"default": "deny",
"tools": {
"on_cdp_event": {
"limits": [
{
"counter": "on_cdp_event_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}on_cdp_event 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.
设置监听CDP事件 应该先运行cdp 命令 激活对应的域，比如 Network.enable. It is categorised as a Execute tool in the DrissionPageMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DrissionPage MCP server in PolicyLayer and add a rule for on_cdp_event: 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 DrissionPageMCP. Nothing to install.
on_cdp_event 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 on_cdp_event 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 on_cdp_event. 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.
on_cdp_event is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.