vitrine_publish · Vitrine MCP Server MCP: Risk & Policy

WHAT IT DOES

What vitrine_publish does on Vitrine MCP Server

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

This tool creates or modifies data (publishing status of a model) reversibly—models can be unpublished to undo the action. It is not destructive since publishing does not delete or permanently remove data. It is not Execute since it does not run arbitrary code or shell commands. The publish action is a state modification rather than a retrieval, placing it in the Write category.

From the tool's definition Tool name is 'vitrine_publish' with description 'Publish or unpublish a model. Published models are embeddable.' The publish/unpublish actions modify the state and visibility of models in the platform, making them accessible or inaccessible for embedding.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

vitrine_publish Rate-limited

vitrine_publish 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_publish": {
      "limits": [
        {
          "counter": "vitrine_publish_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_publish

What does the vitrine_publish tool do? +

Publish or unpublish a model. Published models are embeddable. 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_publish? +

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

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

Can I rate-limit vitrine_publish? +

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

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

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