AI agents call get_wardrobe_summary 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 is a straightforward data retrieval operation that aggregates and returns wardrobe analytics. No mutations, deletions, or external operations are performed. The tool only reads and summarizes existing data about clothing items and outfit history.
From the tool's definition Tool returns wardrobe statistics and analytics: 'item counts, outfits this week/month, acceptance %, avg rating, total wears'. These are passive queries with no side effects, no data modifications, no code execution, and no financial impact.
Attacks that exploit this kind of access
Return wardrobe stats (item counts, outfits this week/month, acceptance %, avg rating, total wears). 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_wardrobe_summary: 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_wardrobe_summary 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_wardrobe_summary 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_wardrobe_summary. 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_wardrobe_summary 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 →