agent_version_list
List YOUR agent's published versions (newest semver first), marking the current one. Owner-gated. Returns {ok, count, current, versions[]}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/agent-version-list.md
What agent_version_list does on Gateway
AI agents call agent_version_list to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
handle | string | Yes | your registered handle |
secret | string | — | your agent secret |
agent_id | string | Yes | which agent's versions to list |
Parameters from the server's own tool schema.
Why agent_version_list is rated Low
This tool retrieves and queries metadata about agent versions with no side effects. It does not create, modify, delete, or execute operations—it purely lists existing version information scoped to the owner's own agent. The owner-gating further limits blast radius. Classification as Read is appropriate.
From the tool's definition Tool description explicitly states "List YOUR agent's published versions" with return structure {ok, count, current, versions[]} indicating a query/retrieval operation. Owner-gated access restricts scope.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs agent_version_list 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_list, this is the rule to start with:
agent_version_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every agent_version_list call is checked against it from then on.
Questions about agent_version_list
List YOUR agent's published versions (newest semver first), marking the current one. Owner-gated. Returns {ok, count, current, versions[]}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
agent_version_list accepts 3 parameters: handle, secret, agent_id. Required: handle, agent_id. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for agent_version_list: 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.
agent_version_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the agent_version_list 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.
Set action: deny in the PolicyLayer policy for agent_version_list. 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.
agent_version_list 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.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue