The Human Intervention action is how an AI Rule Engine workflow waits for a person: the run pauses, a secure form link is generated, and nothing moves until someone reviews and submits. That guarantee is the point — but until now it came with a catch for AI agents. When an assistant kicked off such a workflow through the MCP server, the run paused, the agent got the link, and that was the end of the conversation. Fire-and-forget.

Not anymore. An AI agent connected over MCP can now read a pending intervention form and submit it on your behalf — so the paused workflow resumes, and the agent brings back the result.

How it works

Say you ask your assistant to run a discount-approval workflow. The run reaches its Human Intervention action and pauses, and the MCP call returns the generated form link instead of a final result. Here is what changes: the agent can now fetch that pending form — its fields, labels, and any values prefilled from the run’s context — and show you what is being asked. You answer in the conversation (“approve it, but cap it at 15%”), the agent fills in the form and submits, and the workflow resumes exactly as if you had opened the link and typed the answers yourself.

You are still the one deciding. The change is purely in how you deliver the decision: through your assistant, in the same conversation where you started the work, instead of context-switching to a browser form.

You control which forms agents may touch

Every Human Intervention action now has an Allow AI agents to submit switch:

On (the default) — agents over MCP can read the pending form and submit it on your behalf.
Off — the form can only be submitted through the web link. Agents can still see what is being asked, but the submission itself must happen by a person, in the browser. Use this for sign-offs that should never be delegated — the “walk over and click it yourself” tier of approvals.

Because the switch lives on the action, one workflow can mix both: routine data-entry steps an agent may complete, and a final human sign-off it may not.

The same safeguards, agent or not

Agent submissions go through the same checks as the public form page. An expired link is rejected. A link at its maximum number of uses is rejected. Each accepted submission consumes a use. And submitting is bounded by the MCP connection’s own permissions — an agent can only act within the rule sets its token is allowed to reach. The whole pause-and-resume sequence stays stitched together under one correlation id in your run logs, so the audit trail reads the same whether a person or an agent pressed submit.

Why this matters

Human-in-the-loop and AI agents used to pull in opposite directions: the more review checkpoints you added, the less an agent could actually finish. Now the checkpoint and the agent cooperate. The workflow still stops and waits for a human decision — but the human can make that decision wherever they already are, and the agent carries it the last mile.

Visit RuleEngine.ai to try it.

The AI Rule Engine Team