get_asset_details

Get detailed asset information including spriteFrame sub-assets

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/get-asset-details.md

WHAT IT DOES

What get_asset_details does on Cocos

AI agents call get_asset_details 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 get_asset_details is rated Low

The tool retrieves and queries asset metadata and sub-asset information (spriteFrame details) without any side effects. It performs a read-only operation on existing assets in the Cocos Creator editor project, fitting the Read category. The severity is low because exposure poses minimal risk—an AI agent misusing it would only gather information about existing assets, not modify or destroy data.

From the tool's definition Tool name is 'get_asset_details' and description states 'Get detailed asset information' with no modification, deletion, or execution implied. This is a query/retrieval operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

get_asset_details Allowed

get_asset_details 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": {
    "get_asset_details": {}
  }
}

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 get_asset_details call is checked against it from then on.

FAQ

Questions about get_asset_details

What does the get_asset_details tool do? +

Get detailed asset information including spriteFrame sub-assets. 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 get_asset_details? +

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

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

Can I rate-limit get_asset_details? +

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

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

get_asset_details 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_event_details on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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