Update a collection item: name, description, rating, or tags
AI agents use update_collection_item 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 data (collection item metadata) in a way that can be undone or corrected. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely retrieve information (Read).
From the tool's definition Tool name contains 'update' and description states 'Update a collection item: name, description, rating, or tags' — these are reversible modifications to metadata fields.
Attacks that exploit this kind of access
Update a collection item: name, description, rating, or tags. 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 update_collection_item: 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.
update_collection_item 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 update_collection_item 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 update_collection_item. 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.
update_collection_item 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 →