Collect a design node from the current document into a named collection for reuse across projects
AI agents use collect_asset to create or update resources in AI-Canvas MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AI-Canvas MCP Server environment.
This tool creates or modifies a collection by aggregating design nodes—a data creation/modification action. It does not execute arbitrary code, delete irreversibly, or move funds.
From the tool's definition The tool description explicitly states it will 'Collect a design node from the current document into a named collection for reuse across projects.' This involves creating/modifying a named collection by adding design assets, which is a reversible write…
Attacks that exploit this kind of access
Collect a design node from the current document into a named collection for reuse across projects. It is categorised as a Write tool in the AI-Canvas MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AI-Canvas MCP Server MCP server in PolicyLayer and add a rule for collect_asset: 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 AI-Canvas MCP Server. Nothing to install.
collect_asset 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 collect_asset 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 collect_asset. 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.
collect_asset is provided by the AI-Canvas MCP Server MCP server (laoluojuhai/ai-canvas). 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 →