Get current workflow v2 session status without advancing. Returns: - Overall progress (phase, percent complete) - Summary of findings by severity - Summary of proposed changes - Optionally: status of all files Use this to check on workflow progress or recover context after interruption.
AI agents call workflow_status 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.
This tool retrieves or queries the current state of a workflow session and returns status information. It performs no modifications, deletions, or external operations—only passive introspection. The returned data (progress percentage, findings summary, proposed changes summary) are informational outputs that allow context recovery after interruption.
From the tool's definition Tool description explicitly states 'Get current workflow v2 session status without advancing' and 'check on workflow progress'. Returns status information (progress, findings, proposed changes) with no side effects or modifications indicated.
Risk signalsBulk/mass operation — affects multiple targets
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 Bc Code Intelligence, 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.
Get current workflow v2 session status without advancing. Returns: - Overall progress (phase, percent complete) - Summary of findings by severity - Summary of proposed changes - Optionally: status of all files Use this to check on workflow progress or recover context after interruption. 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_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 Bc Code Intelligence. 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 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.