cancellable-wait
Sleeps up to maxMs unless the task runner aborts us.
This record as markdown: /tools/frontmcp/cancellable-wait.md
What cancellable-wait does on Frontmcp
AI agents invoke cancellable-wait to trigger actions in Frontmcp. 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 cancellable-wait is rated High
This tool executes a sleep/wait operation that can be interrupted by task runner abortion. While not destructive or harmful by itself, it triggers external operations (sleep, cancellation handling) whose effects depend on the maxMs argument and cancellation state.
From the tool's definition Tool performs active execution: "Sleeps up to maxMs unless the task runner aborts us" indicates runtime control flow manipulation and task lifecycle management.
Attacks that exploit this kind of access
The rule that runs cancellable-wait safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Frontmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cancellable-wait, this is the rule to start with:
cancellable-wait 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 Frontmcp, apply this rule, and every cancellable-wait call is checked against it from then on.
Questions about cancellable-wait
Sleeps up to maxMs unless the task runner aborts us. It is categorised as a Execute tool in the Frontmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Front MCP server in PolicyLayer and add a rule for cancellable-wait: 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 Frontmcp. Nothing to install.
cancellable-wait 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 cancellable-wait 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 cancellable-wait. 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.
cancellable-wait is provided by the Front MCP server (agentfront/frontmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Front, and thousands of servers like it.
Across the catalogue