query_gizmo_tool_name

Get current Gizmo tool name

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/query-gizmo-tool-name.md

WHAT IT DOES

What query_gizmo_tool_name does on Cocos

AI agents call query_gizmo_tool_name 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.

RISK

Why query_gizmo_tool_name is rated Low

This tool queries the state of the current Gizmo tool in the Cocos Creator editor. It is a simple getter that retrieves existing information about editor state without altering it. No data is created, modified, deleted, or executed. This falls squarely into the Read category with low severity since misuse poses minimal risk.

From the tool's definition Tool name contains 'query' and description states 'Get current Gizmo tool name' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

query_gizmo_tool_name Allowed

query_gizmo_tool_name is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "query_gizmo_tool_name": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about query_gizmo_tool_name

What does the query_gizmo_tool_name tool do? +

Get current Gizmo tool name. It is categorised as a Read tool in the Cocos MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_gizmo_tool_name? +

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

query_gizmo_tool_name is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit query_gizmo_tool_name? +

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

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

query_gizmo_tool_name 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

get_cocktail_by_name on Cocktails RAG MCP Server →claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →