Get the next action to perform in a workflow session. Call this when you
AI agents call workflow_next 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 workflow state information to return the next action. It has no side effects on data (no creation, modification, or deletion) and does not execute code or trigger external operations. It is a read-only operation that fetches workflow navigation information, making it a Read category tool with low severity.
From the tool's definition Tool name 'workflow_next' and description 'Get the next action to perform in a workflow session' indicates a query operation that retrieves the next step in a workflow without modifying data or executing external operations.
Documented attack patterns abuse exactly the kind of access workflow_next 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_next:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_next": {}
}
}workflow_next 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 the next action to perform in a workflow session. Call this when you. 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_next: 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_next 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_next 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_next. 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_next 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.