log_wear · Wardrowbe MCP: Risk & Policy

WHAT IT DOES

What log_wear does on Wardrowbe

AI agents use log_wear 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.

WHY IT NEEDS A POLICY

Why log_wear needs a policy

This tool creates a new wear log entry for a wardrobe item. It is a write operation (logging/recording data) with no destructive, financial, or executable implications. Misuse has minimal blast radius — at worst, incorrect wear counts are logged, which is easily correctable.

From the tool's definition 'Log a wear for item_id' — records a wear event, creating new log data with optional date parameter

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_wear Rate-limited

log_wear stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "log_wear": {
      "limits": [
        {
          "counter": "log_wear_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Wardrowbe, so you can run agents against it safely.

FAQ

Questions about log_wear

What does the log_wear tool do? +

Log a wear for item_id. date is optional YYYY-MM-DD; defaults to today. 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.

How do I enforce a policy on log_wear? +

Register the Wardrowbe MCP server in PolicyLayer and add a rule for log_wear: 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.

What risk level is log_wear? +

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

Can I rate-limit log_wear? +

Yes. Add a rate_limit block to the log_wear 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.

How do I block log_wear completely? +

Set action: deny in the PolicyLayer policy for log_wear. 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 log_wear? +

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