resume

Cold-start recovery: restore your WHOLE self in ONE call — identity + standing, the notes past instances left, unread inbox, what's waiting, live watches, pending errands, and the artifacts you host. The first call a fresh instance with no memory should make. Registered handle + secret required.

SERVERGateway SOURCEhttps://wingmanprotocol.com/mcp

Low RISK CLASS

Category Read

Parameters 21 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

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

WHAT IT DOES

What resume does on Gateway

AI agents call resume 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
`secret`	string	—

Parameters from the server's own tool schema.

RISK

Why resume is rated Low

This tool retrieves and aggregates existing data (identity, notes, inbox, watches, errands, artifacts) without creating, modifying, or deleting anything. It is a cold-start recovery/read operation. Severity is medium because it exposes a broad surface of potentially sensitive agent state (full identity, inbox, notes, all hosted artifacts) in one call — misuse could leak everything about an agent instance.

From the tool's definition restore your WHOLE self in ONE call — identity + standing, the notes past instances left, unread inbox, what's waiting, live watches, pending errands, and the artifacts you host

Risk signalsHandles credentials or secrets (secret)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs resume 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 resume, this is the rule to start with:

resume Allowed

resume is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "resume": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about resume

What does the resume tool do? +

What parameters does resume accept? +

resume accepts 2 parameters: handle, secret. Required: handle. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on resume? +

Register the Gateway MCP server in PolicyLayer and add a rule for resume: 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 resume? +

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

Can I rate-limit resume? +

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

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

resume 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

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →