vitrine_login · Vitrine MCP Server MCP: Risk & Policy

WHAT IT DOES

What vitrine_login does on Vitrine MCP Server

AI agents invoke vitrine_login to trigger actions in Vitrine MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why vitrine_login needs a policy

The tool triggers an external browser operation (opening a browser window) to perform authentication. This is an Execute-category action because it initiates an external operation whose effects depend on user interaction, rather than simply reading data or writing records directly.

From the tool's definition Opens a browser to sign in or sign up

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vitrine_login Rate-limited

vitrine_login stays usable, but rate-capped — a runaway agent can't fire it dozens of times 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_login": {
      "limits": [
        {
          "counter": "vitrine_login_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_login

What does the vitrine_login tool do? +

Connect your Vitrine account. Opens a browser to sign in or sign up. It is categorised as a Execute tool in the Vitrine MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on vitrine_login? +

Register the Vitrine MCP Server MCP server in PolicyLayer and add a rule for vitrine_login: 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_login? +

vitrine_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit vitrine_login? +

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

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

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