vitrine_feedback · Vitrine MCP Server MCP: Risk & Policy

WHAT IT DOES

What vitrine_feedback does on Vitrine MCP Server

AI agents use vitrine_feedback to create or update resources in Vitrine MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Vitrine MCP Server environment.

WHY IT NEEDS A POLICY

Why vitrine_feedback needs a policy

This tool creates a GitHub issue, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. Misuse could create spam issues but has minimal blast radius.

From the tool's definition Submit a bug report or feature request. Creates a GitHub issue automatically.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vitrine_feedback Rate-limited

vitrine_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": {
    "vitrine_feedback": {
      "limits": [
        {
          "counter": "vitrine_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 Vitrine MCP Server, so you can run agents against it safely.

FAQ

Questions about vitrine_feedback

What does the vitrine_feedback tool do? +

Submit a bug report or feature request. Creates a GitHub issue automatically. It is categorised as a Write tool in the Vitrine MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on vitrine_feedback? +

Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_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 Vitrine MCP Server. Nothing to install.

What risk level is vitrine_feedback? +

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

Can I rate-limit vitrine_feedback? +

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

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

vitrine_feedback is provided by the Vitrine MCP Server MCP server (vitrine3d/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.