AI agents call get_cdp_event_data to retrieve information from DrissionPageMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves Chrome DevTools Protocol (CDP) event data that has already been collected by callback functions. It is a passive read operation that queries stored event data. There are no side effects, no code execution, no data modification, and no resource deletion. The most severe action would be information disclosure if sensitive data were exposed, but this is a standard monitoring/debugging capability.
From the tool's definition Tool name 'get_cdp_event_data' and description '获取CDP事件回调函数收集到的数据' (retrieve CDP event callback function collected data) indicate data retrieval without modification or execution.
Documented attack patterns abuse exactly the kind of access get_cdp_event_data 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 get_cdp_event_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_cdp_event_data": {}
}
}get_cdp_event_data 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.
获取CDP事件回调函数收集到的数据. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.
Register the DrissionPage MCP server in PolicyLayer and add a rule for get_cdp_event_data: 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.
get_cdp_event_data 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 get_cdp_event_data 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 get_cdp_event_data. 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.
get_cdp_event_data 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.