AI agents call workflow_status to retrieve information from Codex Workflows MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the status of an existing workflow run and returns summary information. It performs no mutations, deletions, or external operations. It is a straightforward read operation with minimal blast radius if misused by an agent.
From the tool's definition Tool description states 'Read the current run summary' — a retrieval operation with no modifications or side effects.
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 Codex Workflows MCP Server, 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.
Read the current run summary. It is categorised as a Read tool in the Codex Workflows MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Codex Workflows MCP Server 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 Codex Workflows MCP Server. 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 Codex Workflows MCP Server MCP server (robzilla1738/codex-workflows). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 10 Codex Workflows MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
10 Codex Workflows MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.