change_gizmo_coordinate

Change coordinate system

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

Medium RISK CLASS

Category Write

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/change-gizmo-coordinate.md

WHAT IT DOES

What change_gizmo_coordinate does on Cocos

AI agents use change_gizmo_coordinate to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.

RISK

Why change_gizmo_coordinate is rated Medium

Changing the gizmo coordinate system modifies editor display/interaction settings (local vs world coordinates). This is a reversible editor state change with minimal blast radius, categorized as Write.

From the tool's definition Change coordinate system

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs change_gizmo_coordinate 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_coordinate, this is the rule to start with:

change_gizmo_coordinate Rate-limited

change_gizmo_coordinate stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "change_gizmo_coordinate": {
      "limits": [
        {
          "counter": "change_gizmo_coordinate_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about change_gizmo_coordinate

What does the change_gizmo_coordinate tool do? +

Change coordinate system. It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on change_gizmo_coordinate? +

Register the Cocos MCP server in PolicyLayer and add a rule for change_gizmo_coordinate: 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 change_gizmo_coordinate? +

change_gizmo_coordinate is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit change_gizmo_coordinate? +

Yes. Add a rate_limit block to the change_gizmo_coordinate 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 change_gizmo_coordinate completely? +

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

change_gizmo_coordinate 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 →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →