This record as markdown: /tools/caravanglory-cocos-mcp-server/get-asset-info.md
What get_asset_info does on Cocos
AI agents call get_asset_info 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_asset_info is rated Low
This tool retrieves or queries asset information from the Cocos Creator editor without causing any state changes, side effects, or irreversible operations. It fits the Read category definition of retrieving data with no side effects. The severity is low because misuse by an AI agent would only expose existing asset metadata, posing minimal security risk to the project or system.
From the tool's definition Tool name 'get_asset_info' and description 'Get asset information' indicate retrieval of metadata about assets without modification, creation, or deletion. No parameters or side effects are described.
Attacks that exploit this kind of access
The rule that runs get_asset_info 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_asset_info, this is the rule to start with:
get_asset_info 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_asset_info call is checked against it from then on.
Questions about get_asset_info
Get asset information. 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_asset_info: 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_asset_info 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_asset_info 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_asset_info. 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_asset_info 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