Report progress on current workflow action and get the next action. Call this after completing each action (analyzing a file, applying a topic, converting an instance). Include any findings, proposed changes, and topics to add to the checklist. The engine updates session state and returns the nex...
AI agents call workflow_progress to retrieve information from Bc Code Intelligence without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool's primary purpose is to report progress and receive the next action in a workflow pipeline. While it 'updates session state,' this appears to be internal coordination/bookkeeping within the MCP session rather than creating, modifying, or deleting external resources. It functions as a workflow orchestration checkpoint — essentially reading what to do next.
From the tool's definition 'Report progress on current workflow action and get the next action' — this tool reports state and retrieves the next action from the engine; it updates session state internally but the primary effect from an external/security standpoint is reading workflow…
Documented attack patterns abuse exactly the kind of access workflow_progress gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Bc Code Intelligence, and nothing reaches the server without passing your rules. This is the rule we recommend for workflow_progress:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_progress": {}
}
}workflow_progress 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.
Report progress on current workflow action and get the next action. Call this after completing each action (analyzing a file, applying a topic, converting an instance). Include any findings, proposed changes, and topics to add to the checklist. The engine updates session state and returns the next action to perform. It is categorised as a Read tool in the Bc Code Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for workflow_progress: 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 Bc Code Intelligence. Nothing to install.
workflow_progress 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_progress 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_progress. 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_progress is provided by the Bc Code Intelligence MCP server (jeremyvyska/bc-code-intelligence-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Bc Code Intelligence, 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.
27 Bc Code Intelligence tools catalogued and risk-classified — across an index of 43,000+ MCP servers.