This record as markdown: /tools/caravanglory-cocos-mcp-server/set-grid-visible.md
What set_grid_visible does on Cocos
AI agents use set_grid_visible 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.
Why set_grid_visible is rated Medium
Toggling grid visibility is a UI preference change that modifies editor state. It does not retrieve data (Read), execute arbitrary code (Execute), permanently delete content (Destructive), or involve financial operations (Financial). It is reversible and represents a minor configuration change. Classified as Write rather than Other because it actively modifies application state.
From the tool's definition Tool name is 'set_grid_visible' with description 'Show/hide grid'. This modifies the visual editor state (grid visibility setting) in the Cocos Creator editor.
Attacks that exploit this kind of access
The rule that runs set_grid_visible 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 set_grid_visible, this is the rule to start with:
set_grid_visible 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Cocos, apply this rule, and every set_grid_visible call is checked against it from then on.
Questions about set_grid_visible
Show/hide grid. 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.
Register the Cocos MCP server in PolicyLayer and add a rule for set_grid_visible: 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.
set_grid_visible is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set_grid_visible 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 set_grid_visible. 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.
set_grid_visible 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