change_gizmo_tool
A execute tool on the Cocos MCP server.
This record as markdown: /tools/caravanglory-cocos-mcp-server/change-gizmo-tool.md
What change_gizmo_tool does on Cocos
AI agents invoke change_gizmo_tool 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.
Why change_gizmo_tool is rated High
Changing the gizmo tool in the Cocos Creator editor is an editor UI state change that triggers an external operation in the editor. It doesn't read data, write persistent data, or destroy anything - it switches the active manipulation tool (move/rotate/scale/etc.). The description is minimal, so confidence is moderate. Severity is low as misuse only affects editor UI state, not assets or project data.
From the tool's definition 'Change Gizmo tool' - changes the active gizmo/transformation tool in the editor
Attacks that exploit this kind of access
The rule that runs change_gizmo_tool 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 change_gizmo_tool, this is the rule to start with:
change_gizmo_tool 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every change_gizmo_tool call is checked against it from then on.
Questions about change_gizmo_tool
change_gizmo_tool is a execute tool on the Cocos MCP server. 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.
Register the Cocos MCP server in PolicyLayer and add a rule for change_gizmo_tool: 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.
change_gizmo_tool 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 change_gizmo_tool 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 change_gizmo_tool. 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.
change_gizmo_tool 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