Medium Risk

update_existing_item

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 Yo...

Accepts URL/endpoint input (url); High parameter count (23 properties)

Part of the Caffeinated Wardrobe MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

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. Intercept'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.

michelle-caffeinated-wardrobe.yaml
tools:
  update_existing_item:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Caffeinated Wardrobe policy for all 20 tools.

Tool Name update_existing_item
Category Write
Risk Level Medium

View all 20 tools →

Agents calling write-class tools like update_existing_item have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the update_existing_item tool do? +

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.

How do I enforce a policy on update_existing_item? +

Add a rule in your Intercept YAML policy under the tools section for update_existing_item. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Caffeinated Wardrobe MCP server.

What risk level is update_existing_item? +

update_existing_item is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_existing_item? +

Yes. Add a rate_limit block to the update_existing_item rule in your Intercept 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.

How do I block update_existing_item completely? +

Set action: deny in the Intercept 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.

What MCP server provides update_existing_item? +

update_existing_item is provided by the Caffeinated Wardrobe MCP server (michelle/caffeinated-wardrobe). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Caffeinated Wardrobe

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.