deploy_prompt_version · Respan MCP Server MCP: Risk & Policy

WHAT IT DOES

What deploy_prompt_version does on Respan MCP Server

AI agents invoke deploy_prompt_version to trigger actions in Respan 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 deploy_prompt_version needs a policy

This tool deploys/activates a prompt version for use in experiments and workflows. While it does not delete or create financial transactions, it triggers an operational change that affects the behavior of downstream systems (experiments and workflows will now use the deployed version).

From the tool's definition Deploy a specific prompt version, making it the active version that experiments (and other workflows) will use.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

deploy_prompt_version Rate-limited

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

FAQ

Questions about deploy_prompt_version

What does the deploy_prompt_version tool do? +

Deploy a specific prompt version, making it the active version that experiments (and other workflows) will use. Background: when you create a prompt version, it starts as a draft (not deployed). The platform requires at least one DEPLOYED version before a prompt can be referenced by version number in experiments or other workflows. If you call create_experiment with a prompt workflow and see. It is categorised as a Execute tool in the Respan 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 deploy_prompt_version? +

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

What risk level is deploy_prompt_version? +

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

Can I rate-limit deploy_prompt_version? +

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

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

deploy_prompt_version is provided by the Respan MCP Server MCP server (respanai/respan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.