Complete a Workflow Engine v2 session and generate the final report. Call this when all files have been processed (next_action.type ===
AI agents use workflow_complete to create or update resources in Bc Code Intelligence — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Bc Code Intelligence environment.
This tool creates or commits a final report, which is a data modification operation. It marks workflow completion and generates output that persists, making it Write rather than Read. While report generation is typically low-risk, in the context of Business Central development assistance, finalizing workflows could trigger downstream processes or lock workflow state irreversibly, warranting medium severity.
From the tool's definition Tool name 'workflow_complete' combined with description 'Complete a Workflow Engine v2 session and generate the final report' indicates the tool modifies state by finalizing a workflow session and creating a report artifact.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access workflow_complete 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_complete:
{
"version": "1",
"default": "deny",
"tools": {
"workflow_complete": {
"limits": [
{
"counter": "workflow_complete_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}workflow_complete stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Complete a Workflow Engine v2 session and generate the final report. Call this when all files have been processed (next_action.type ===. It is categorised as a Write tool in the Bc Code Intelligence MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Bc Code Intelligence MCP server in PolicyLayer and add a rule for workflow_complete: 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_complete is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the workflow_complete 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_complete. 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_complete 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.