clear_broadcast_log
Clear the broadcast messages log
This record as markdown: /tools/caravanglory-cocos-mcp-server/clear-broadcast-log.md
What clear_broadcast_log does on Cocos
AI agents call clear_broadcast_log to permanently remove resources in Cocos, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why clear_broadcast_log is rated Critical
Clearing a log is an irreversible destructive action — once the broadcast messages log is cleared, the historical data cannot be recovered. Severity is medium because it only affects log data, not core project assets or code.
From the tool's definition Clear the broadcast messages log
Attacks that exploit this kind of access
The rule that runs clear_broadcast_log 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 clear_broadcast_log, this is the rule to start with:
clear_broadcast_log is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every clear_broadcast_log call is checked against it from then on.
Questions about clear_broadcast_log
Clear the broadcast messages log. It is categorised as a Destructive tool in the Cocos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Cocos MCP server in PolicyLayer and add a rule for clear_broadcast_log: 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.
clear_broadcast_log is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the clear_broadcast_log 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 clear_broadcast_log. 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.
clear_broadcast_log 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.
More on Cocos, and thousands of servers like it.
Across the catalogue