AI agents call get_most_worn_items to retrieve information from Wardrowbe without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries analytics data about wardrobe usage patterns. It retrieves and returns information without modifying, deleting, or executing any operations. The 'limit' parameter (1–10) controls result volume but does not change the nature of the operation. This is a straightforward Read operation with minimal risk.
From the tool's definition Tool name is 'get_most_worn_items' and description states 'List the user's most-worn items (analytics-derived)'. The verb 'List' and use of 'get_' prefix indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List the user's most-worn items (analytics-derived). limit 1–10. It is categorised as a Read tool in the Wardrowbe MCP Server, which means it retrieves data without modifying state.
Register the Wardrowbe MCP server in PolicyLayer and add a rule for get_most_worn_items: 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.
get_most_worn_items is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_most_worn_items 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 get_most_worn_items. 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.
get_most_worn_items 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 →