Extract a Business Central snapshot (.snap) file to analyze debug traces, AL source code, and execution flow. Snapshots are ZIP archives containing .mdc debug trace files and .al source files. Returns temp directory path where files can be read using standard file tools.
AI agents call extract_bc_snapshot 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.
extract_bc_snapshot decompresses an archive and exposes its contents for inspection. It is purely a read operation that retrieves and organizes data for analysis. While it creates temporary files, these are staging artifacts for read access, not persistent data creation or modification. The tool has no side effects on the Business Central system, code repositories, or financial data.
From the tool's definition Tool 'extracts' snapshot files to enable 'analysis' and 'reading' of debug traces and source code. Returns a 'temp directory path where files can be read'—no modifications, deletions, or external operations are performed.
Documented attack patterns abuse exactly the kind of access extract_bc_snapshot 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 extract_bc_snapshot:
{
"version": "1",
"default": "deny",
"tools": {
"extract_bc_snapshot": {}
}
}extract_bc_snapshot 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.
Extract a Business Central snapshot (.snap) file to analyze debug traces, AL source code, and execution flow. Snapshots are ZIP archives containing .mdc debug trace files and .al source files. Returns temp directory path where files can be read using standard file tools. 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 extract_bc_snapshot: 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.
extract_bc_snapshot 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 extract_bc_snapshot 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 extract_bc_snapshot. 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.
extract_bc_snapshot 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.