AI agents use import_avatar to create or update resources in Clo3d — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Clo3d environment.
The tool creates or modifies project state by loading an avatar asset into CLO3D, similar to uploading or adding content. This is a Write action (reversible; the avatar can be removed or replaced). It is not Read (it changes state), Execute (no arbitrary code/command execution), Destructive (reversible), Financial (no money involved), or Other.
From the tool's definition import_avatar imports an avatar file into the scene — this modifies the scene's state by adding content, which is a reversible write operation.
Attacks that exploit this kind of access
Import an avatar file into the scene. It is categorised as a Write tool in the Clo3d MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Clo3d MCP server in PolicyLayer and add a rule for import_avatar: 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 Clo3d. Nothing to install.
import_avatar 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 import_avatar 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 import_avatar. 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.
import_avatar is provided by the Clo3d MCP server (lilbonner/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →