agent_version_list

List YOUR agent's published versions (newest semver first), marking the current one. Owner-gated. Returns {ok, count, current, versions[]}.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp
Low RISK CLASS
Category Read
Parameters 32 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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.

ParameterTypeRequiredDescription
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)

Questions about agent_version_list

What does the agent_version_list tool do? +

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.

What parameters does agent_version_list accept? +

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.

How do I enforce a policy on agent_version_list? +

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.

What risk level is agent_version_list? +

agent_version_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit agent_version_list? +

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.

How do I block agent_version_list completely? +

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.

What MCP server provides agent_version_list? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Gateway's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.