Update an existing wardrobe item. For brands, colors, and stores, you can provide either the name or ID: - brand: "Nike" (auto-creates if not found) OR brand_id: UUID - color: "Blue" (auto-creates if not found) OR color_id: UUID - store: "Amazon" (auto-creates if not found) OR store_id: UUID You ...
Risk signalsAccepts URL/endpoint input (url) · High parameter count (23 properties)
Part of the Caffeinated Wardrobe server.
Free to start. No card required.
AI agents use update_existing_item to create or modify resources in Caffeinated Wardrobe. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_existing_item repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Caffeinated Wardrobe.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_existing_item": {
"limits": [
{
"counter": "update_existing_item_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Caffeinated Wardrobe policy for all 20 tools.
These attack patterns abuse exactly the kind of access update_existing_item gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Update an existing wardrobe item. For brands, colors, and stores, you can provide either the name or ID: - brand: "Nike" (auto-creates if not found) OR brand_id: UUID - color: "Blue" (auto-creates if not found) OR color_id: UUID - store: "Amazon" (auto-creates if not found) OR store_id: UUID You can also provide image_urls to upload images from publicly accessible URLs. Images will be uploaded after the item is updated. If any image URLs fail to upload, the item will still be updated successfully. No need to check if brands/colors/stores exist first - the system handles this automatically.. It is categorised as a Write tool in the Caffeinated Wardrobe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Caffeinated Wardrobe MCP server in PolicyLayer and add a rule for update_existing_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 Caffeinated Wardrobe. Nothing to install.
update_existing_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_existing_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_existing_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_existing_item is provided by the Caffeinated Wardrobe MCP server (michelle/caffeinated-wardrobe). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Caffeinated Wardrobe tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.