Check if the user has requested to re-run any nodes. Call this after plan_completed to allow users to re-run specific nodes or re-run from a node to the end. Returns immediately if there\
AI agents call check_rerun 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.
This tool queries the system state to determine whether a user has requested plan re-execution. It has no side effects, does not modify data, and does not trigger execution — it merely reads/polls existing approval status. The actual re-execution would be handled by separate tools (likely plan_completed or execute operations). This is a pure Read operation with minimal risk.
From the tool's definition Tool description states it 'Check[s] if the user has requested to re-run any nodes' and 'Returns immediately if there' — the verb is 'check' and 'returns', indicating a query/polling operation that retrieves user input state without making changes.
Documented attack patterns abuse exactly the kind of access check_rerun 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 check_rerun:
{
"version": "1",
"default": "deny",
"tools": {
"check_rerun": {}
}
}check_rerun is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Check if the user has requested to re-run any nodes. Call this after plan_completed to allow users to re-run specific nodes or re-run from a node to the end. Returns immediately if there\. It is categorised as a Read tool in the Overture MCP Server, which means it retrieves data without modifying state.
Register the Overture MCP server in PolicyLayer and add a rule for check_rerun: 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.
check_rerun 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 check_rerun 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 check_rerun. 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.
check_rerun 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.
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.