agent_version_publish

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Medium RISK CLASS

Category Write

Parameters 72 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/com-wingmanprotocol-agent-gateway/agent-version-publish.md

WHAT IT DOES

What agent_version_publish does on Gateway

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

Parameter	Type	Required	Description
`bump`	string	—	major \| minor \| patch (default patch)
`notes`	string	—	optional changelog note (≤2000 chars)
`handle`	string	Yes	your registered handle (owner-gated)
`secret`	string	—	your agent secret
`payload`	object	—	the versioned config/payload (string or JSON object; ≤200KB)
`version`	string	—	explicit semver X.Y.Z (overrides bump)
`agent_id`	string	Yes	which agent to version (your label)

Parameters from the server's own tool schema.

RISK

Why agent_version_publish is rated Medium

Publishing a new version of an agent's configuration is a state-modifying operation that creates new versioned artifacts. It is reversible (subsequent publishes can change the current version) and not destructive (immutable versions remain).

From the tool's definition Tool description states: 'Publish a new immutable version of YOUR agent's config/payload' and 'The new version becomes current.' This creates/modifies the agent's version state and configuration in a reversible manner (can publish new versions).

Risk signalsHandles credentials or secrets (secret) · Accepts raw HTML/template content (payload)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs agent_version_publish safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For agent_version_publish, this is the rule to start with:

agent_version_publish Rate-limited

agent_version_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": {
    "agent_version_publish": {
      "limits": [
        {
          "counter": "agent_version_publish_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every agent_version_publish call is checked against it from then on.

FAQ

Questions about agent_version_publish

What does the agent_version_publish tool do? +

Publish a new immutable version of YOUR agent's config/payload. Owner-gated. Give an explicit 'version' (X.Y.Z) or a 'bump' (major/minor/patch, default patch) off the latest. The new version becomes current. Returns {ok, version, is_current, previous}. It is categorised as a Write tool in the Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does agent_version_publish accept? +

agent_version_publish accepts 7 parameters: bump, notes, handle, secret, payload, version, agent_id. Required: handle, agent_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on agent_version_publish? +

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

What risk level is agent_version_publish? +

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

Can I rate-limit agent_version_publish? +

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

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

agent_version_publish is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Gateway, and thousands of servers like it.

This server

All 271 Gateway tools →

Across the catalogue

team_manager_kill_agent on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →