Check current workflow progress and session state
AI agents call workflow_status 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 retrieves and displays workflow progress and session state information. It has no side effects—it does not create, modify, delete, or execute anything. The action is purely informational (check/query), placing it squarely in the Read category. The low severity reflects minimal blast radius: misuse would only expose status information rather than cause system damage or unintended operations.
From the tool's definition Tool name 'workflow_status' and description 'Check current workflow progress and session state' indicate a read-only query operation that retrieves status information without modifying any state or executing external operations.
Documented attack patterns abuse exactly the kind of access workflow_status 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 workflow_status:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_status": {}
}
}workflow_status 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 current workflow progress and session state. 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 workflow_status: 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.
workflow_status 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 workflow_status 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 workflow_status. 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.
workflow_status 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.