AI agents invoke response_received_listener_stop 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 stops a network listener, which is an operational action that changes the monitoring state of the browser automation system. While it doesn't directly execute code or delete data, it modifies the runtime behavior of network interception—a capability that could be misused to hide or mask network communications during automated browser tasks.
From the tool's definition Tool name contains 'listener_stop' and description translates to 'Stop listening to data packets sent by webpage'. This controls network monitoring state via browser automation, affecting what data the system observes from network traffic.
Documented attack patterns abuse exactly the kind of access response_received_listener_stop 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 response_received_listener_stop:
{
"version": "1",
"default": "deny",
"tools": {
"response_received_listener_stop": {
"limits": [
{
"counter": "response_received_listener_stop_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}response_received_listener_stop 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.
关闭监听网页发送的数据包. 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 response_received_listener_stop: 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.
response_received_listener_stop 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 response_received_listener_stop 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 response_received_listener_stop. 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.
response_received_listener_stop 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.