resume_instance
Put a PAUSED instance back to work: new runs may start again, and background work (cron, the pump, delivery retries, webhooks) resumes. It does NOT restart runs the pause stopped — those have terminal rows and re-running an objective whose partial work is already on the record is the mistake to a...
This record as markdown: /tools/io-github-proagentstore-platform/resume-instance.md
What resume_instance does on ProAgentStore
AI agents invoke resume_instance to trigger actions in ProAgentStore. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why resume_instance is rated High
Resumes a paused agent instance, triggering background operations and new run execution.
From the tool's definition Put a PAUSED instance back to work: new runs may start again
Attacks that exploit this kind of access
The rule that runs resume_instance safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For resume_instance, this is the rule to start with:
resume_instance stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every resume_instance call is checked against it from then on.
Questions about resume_instance
Put a PAUSED instance back to work: new runs may start again, and background work (cron, the pump, delivery retries, webhooks) resumes. It does NOT restart runs the pause stopped — those have terminal rows and re-running an objective whose partial work is already on the record is the mistake to avoid; carry one forward with continue_instance_run instead. Resuming an already-active instance succeeds with. It is categorised as a Execute tool in the ProAgentStore MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for resume_instance: 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 ProAgentStore. Nothing to install.
resume_instance is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resume_instance 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 resume_instance. 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.
resume_instance is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue