This record as markdown: /tools/caravanglory-cocos-mcp-server/compress-textures.md
What compress_textures does on Cocos
AI agents use compress_textures to create or update resources in Cocos, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Cocos environment.
Why compress_textures is rated Medium
Compressing textures modifies asset data (lossy or lossless transformation), but is generally reversible if originals are preserved. It is a write/modify operation on assets rather than a deletion, though batch compression could degrade texture quality if lossy compression is applied. Severity is medium due to potential quality loss across multiple assets at once.
From the tool's definition Batch compress texture assets
Attacks that exploit this kind of access
The rule that runs compress_textures 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 compress_textures, this is the rule to start with:
compress_textures stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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 compress_textures call is checked against it from then on.
Questions about compress_textures
Batch compress texture assets. It is categorised as a Write tool in the Cocos MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Cocos MCP server in PolicyLayer and add a rule for compress_textures: 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.
compress_textures is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the compress_textures 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 compress_textures. 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.
compress_textures 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