This record as markdown: /tools/caravanglory-cocos-mcp-server/get-broadcast-log.md
What get_broadcast_log does on Cocos
AI agents call get_broadcast_log to retrieve information from Cocos without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_broadcast_log is rated Low
This tool queries and retrieves existing broadcast message logs from the Cocos Creator editor. It is a read-only operation that does not modify, delete, execute code, or trigger external operations. The minimal blast radius (at worst, exposure of editor event history) and non-destructive nature clearly place it in the Read category.
From the tool's definition Tool name is 'get_broadcast_log' and description states 'Get recent broadcast messages log' — this retrieves historical log data with no modification or side effects.
Attacks that exploit this kind of access
The rule that runs get_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 get_broadcast_log, this is the rule to start with:
get_broadcast_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every get_broadcast_log call is checked against it from then on.
Questions about get_broadcast_log
Get recent broadcast messages log. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.
Register the Cocos MCP server in PolicyLayer and add a rule for get_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.
get_broadcast_log 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_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 get_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.
get_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.
This server
Across the catalogue