log_wash · Wardrowbe MCP: Risk & Policy

WHAT IT DOES

What log_wash does on Wardrowbe

AI agents use log_wash 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_wash needs a policy

This tool modifies the state of a wardrobe item by resetting its wash counter. It is a reversible data update (the counter can be reset again or incremented), so it falls under Write. The blast radius is low — misuse only affects wear/wash tracking data for clothing items.

From the tool's definition Mark `item_id` as washed. Resets wears_since_wash on the backend.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

log_wash Rate-limited

log_wash 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_wash": {
      "limits": [
        {
          "counter": "log_wash_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_wash

What does the log_wash tool do? +

Mark item_id as washed. Resets wears_since_wash on the backend. 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_wash? +

Register the Wardrowbe MCP server in PolicyLayer and add a rule for log_wash: 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_wash? +

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

Can I rate-limit log_wash? +

Yes. Add a rate_limit block to the log_wash 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_wash completely? +

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

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