Low Risk

get_resume_info

Get detailed information about a paused or failed plan to help resume execution. Returns the current node where execution stopped, list of completed/pending/failed nodes, user-configured field values, selected branches, and other metadata. Use this when resuming a plan that was paused, failed, or...

How to control get_resume_info ↓

AI agents call get_resume_info to retrieve information from Overture without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

This tool purely retrieves and queries state information about a paused or failed plan to support resuming execution. It has no side effects—it does not modify, delete, execute, or move money. The action is purely informational, making it a Read category tool with low severity since it only exposes metadata about plan state.

From the tool's definition Tool name 'get_resume_info' and description indicate it 'Get[s] detailed information' and 'Returns the current node...list of completed/pending/failed nodes...and other metadata' with no modification of state, deletion, code execution, or financial…

Documented attack patterns abuse exactly the kind of access get_resume_info gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Overture, and nothing reaches the server without passing your rules. This is the rule we recommend for get_resume_info:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_resume_info": {}
  }
}

get_resume_info is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Overture — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_resume_info tool do? +

Get detailed information about a paused or failed plan to help resume execution. Returns the current node where execution stopped, list of completed/pending/failed nodes, user-configured field values, selected branches, and other metadata. Use this when resuming a plan that was paused, failed, or loaded from history. It is categorised as a Read tool in the Overture MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_resume_info? +

Register the Overture MCP server in PolicyLayer and add a rule for get_resume_info: 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 Overture. Nothing to install.

What risk level is get_resume_info? +

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

Can I rate-limit get_resume_info? +

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

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

get_resume_info is provided by the Overture MCP server (sixhq/overture). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Overture tool call.

Deterministic rules across all 14 Overture tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

14 Overture tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.