stop_listening

Stop listening for specific broadcast messages

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/stop-listening.md

WHAT IT DOES

What stop_listening does on Cocos

AI agents invoke stop_listening to trigger actions in Cocos. 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.

RISK

Why stop_listening is rated High

This tool executes an operation that changes the runtime behavior of the editor's message subscription system. It is not merely reading data (Read), nor is it creating/modifying persistent assets (Write), nor is it irreversible (Destructive). It triggers an external operation (broadcast message listener management) whose effects depend on which listener is being stopped. This aligns with Execute category.

From the tool's definition Tool name 'stop_listening' and description indicate it modifies the state of a message listener/subscription system within the Cocos Creator editor.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs stop_listening safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Cocos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stop_listening, this is the rule to start with:

stop_listening Rate-limited

stop_listening 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "stop_listening": {
      "limits": [
        {
          "counter": "stop_listening_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every stop_listening call is checked against it from then on.

FAQ

Questions about stop_listening

What does the stop_listening tool do? +

Stop listening for specific broadcast messages. It is categorised as a Execute tool in the Cocos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on stop_listening? +

Register the Cocos MCP server in PolicyLayer and add a rule for stop_listening: 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 Cocos. Nothing to install.

What risk level is stop_listening? +

stop_listening is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit stop_listening? +

Yes. Add a rate_limit block to the stop_listening 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.

How do I block stop_listening completely? +

Set action: deny in the PolicyLayer policy for stop_listening. 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.

What MCP server provides stop_listening? +

stop_listening is provided by the Cocos MCP server (caravanglory/cocos-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Cocos, and thousands of servers like it.

This server

All 157 Cocos tools → High-risk tools on this server →

Across the catalogue

stop_emba_scan on EMBA-MCP →stop_etw_trace on Procmon → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →