get_available_components
Get list of available component types
This record as markdown: /tools/caravanglory-cocos-mcp-server/get-available-components.md
What get_available_components does on Cocos
AI agents call get_available_components 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_available_components is rated Low
This tool simply lists or retrieves available component types from the Cocos Creator editor. It is a pure read operation that queries the system for information without creating, modifying, deleting, or executing any operations. The blast radius of misuse is minimal since an AI agent cannot cause harm by merely reading a list of available components.
From the tool's definition Tool name is 'get_available_components' and description states 'Get list of available component types' — this retrieves or queries data without performing any modifications or side effects.
Attacks that exploit this kind of access
The rule that runs get_available_components 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_available_components, this is the rule to start with:
get_available_components 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_available_components call is checked against it from then on.
Questions about get_available_components
Get list of available component types. 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_available_components: 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_available_components 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_available_components 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_available_components. 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_available_components 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