agent_rollback
Make an existing version of YOUR agent current again (roll back or forward). Owner-gated, idempotent. Returns {ok, current_version, payload}.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/agent-rollback.md
What agent_rollback does on Gateway
AI agents call agent_rollback 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 to roll |
to_version | string | Yes | the semver X.Y.Z to make current |
Parameters from the server's own tool schema.
Why agent_rollback is rated Low
Even though agent_rollback only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsHandles credentials or secrets (secret)
Attacks that exploit this kind of access
The rule that runs agent_rollback 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_rollback, this is the rule to start with:
agent_rollback 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_rollback call is checked against it from then on.
Questions about agent_rollback
Make an existing version of YOUR agent current again (roll back or forward). Owner-gated, idempotent. Returns {ok, current_version, payload}. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
agent_rollback accepts 4 parameters: handle, secret, agent_id, to_version. Required: handle, agent_id, to_version. 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_rollback: 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_rollback 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_rollback 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_rollback. 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_rollback 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