submit_outfit_feedback · Wardrowbe MCP: Risk & Policy

WHAT IT DOES

What submit_outfit_feedback does on Wardrowbe

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

This tool writes user feedback to the wardrobe system. It creates new feedback records or modifies existing ones, fitting the Write category (creates or modifies data reversibly). The severity is low because feedback submission has no destructive effects, no financial impact, no code execution, and limited blast radius—the worst outcome is storing incorrect outfit preferences, which is easily corrected or ignored.

From the tool's definition Tool submits feedback data (rating, wore boolean, notes) to the Wardrowbe API, creating or modifying feedback records.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_outfit_feedback Rate-limited

submit_outfit_feedback 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": {
    "submit_outfit_feedback": {
      "limits": [
        {
          "counter": "submit_outfit_feedback_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 submit_outfit_feedback

What does the submit_outfit_feedback tool do? +

Submit feedback on an outfit. rating 1–5, wore boolean, notes free-form. 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 submit_outfit_feedback? +

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

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

Can I rate-limit submit_outfit_feedback? +

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

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

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