Check if the user has paused execution. Call this before starting each node to respect user pause requests. If wait=true, blocks until the user resumes.
AI agents invoke check_pause to trigger actions in Overture. 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.
This tool governs execution gating: it queries pause state and can block the agent's execution pipeline until a resume signal is received. While it reads a flag, its primary effect is controlling whether execution proceeds, making it an execution-control mechanism rather than a pure read.
From the tool's definition 'Check if the user has paused execution', 'blocks until the user resumes' — the tool actively controls execution flow and can block/gate agent actions based on user state
Documented attack patterns abuse exactly the kind of access check_pause 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_pause:
{
"version": "1",
"default": "deny",
"tools": {
"check_pause": {
"limits": [
{
"counter": "check_pause_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}check_pause 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.
Free to start. No card required.
Check if the user has paused execution. Call this before starting each node to respect user pause requests. If wait=true, blocks until the user resumes. It is categorised as a Execute tool in the Overture MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Overture MCP server in PolicyLayer and add a rule for check_pause: 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_pause 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 check_pause 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_pause. 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_pause 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.