AI agents use restore_item to create or update resources in Wardrowbe — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Wardrowbe environment.
This tool performs a write operation that modifies an item's metadata/state (archival status) in the wardrobe system. It is reversible—the item could be archived again—so it does not qualify as Destructive. The operation has minimal blast radius (affects only a single user's wardrobe item) and no external side effects, making it low severity.
From the tool's definition Tool restores (undeletes/reverts) a previously-archived item, modifying the item's state from archived to active. The word 'restore' indicates a reversible operation that changes data state without permanent destruction.
Attacks that exploit this kind of access
Restore a previously-archived item. It is categorised as a Write tool in the Wardrowbe MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Wardrowbe MCP server in PolicyLayer and add a rule for restore_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 Wardrowbe. Nothing to install.
restore_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 restore_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 restore_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.
restore_item is provided by the Wardrowbe MCP server (saya6k/mcp-wardrowbe). 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 →