refresh_assets

Refresh asset database

SERVERCocos SOURCEcaravanglory/cocos-mcp-server

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/caravanglory-cocos-mcp-server/refresh-assets.md

WHAT IT DOES

What refresh_assets does on Cocos

AI agents invoke refresh_assets to trigger actions in Cocos. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

RISK

Why refresh_assets is rated High

Refreshing the asset database triggers an active scan/rebuild operation in the editor, which goes beyond simply reading data — it causes the editor to re-scan, re-import, or reprocess assets. This is an external operation with side effects (e.g., reimporting assets, updating metadata), placing it in the Execute category.

From the tool's definition Refresh asset database

Attacks that exploit this kind of access

RECOMMENDED RULE

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

refresh_assets Rate-limited

refresh_assets stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh_assets": {
      "limits": [
        {
          "counter": "refresh_assets_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about refresh_assets

What does the refresh_assets tool do? +

Refresh asset database. It is categorised as a Execute tool in the Cocos MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on refresh_assets? +

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

refresh_assets is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit refresh_assets? +

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

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

refresh_assets 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 → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →