Validate that current phase meets all completion requirements before allowing progression
AI agents call validate_phase_completion to retrieve information from Structured Workflow MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a gating check—evaluating state against criteria to permit advancement in a workflow. It retrieves or queries the state of phase completion without creating, modifying, executing external code, or deleting data. The validation is an informational check that informs the next decision in a workflow but does not itself cause side effects.
From the tool's definition The tool is described as a validator that checks whether completion requirements are met before progression.
Documented attack patterns abuse exactly the kind of access validate_phase_completion gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Structured Workflow MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for validate_phase_completion:
{
"version": "1",
"default": "deny",
"tools": {
"validate_phase_completion": {}
}
}validate_phase_completion 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.
Validate that current phase meets all completion requirements before allowing progression. It is categorised as a Read tool in the Structured Workflow MCP MCP Server, which means it retrieves data without modifying state.
Register the Structured Workflow MCP server in PolicyLayer and add a rule for validate_phase_completion: 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 Structured Workflow MCP. Nothing to install.
validate_phase_completion 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 validate_phase_completion 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 validate_phase_completion. 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.
validate_phase_completion is provided by the Structured Workflow MCP server (kingdomseed/structured-workflow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Structured Workflow MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 Structured Workflow MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.