Diagnose local layer (project overrides) path and content issues. Use when local layers fail to load or have 0 topics.
AI agents call diagnose_local_layer 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 and analyzes diagnostic information about local layer configurations and content. It performs read-only inspection to identify issues with path resolution and topic loading, with no side effects on the system or data. The low blast radius reflects that misuse would only surface incorrect or incomplete diagnostic output rather than causing harm.
From the tool's definition Tool name 'diagnose_local_layer' and description 'Diagnose local layer (project overrides) path and content issues' indicate inspection/analysis of existing data. No modification, execution of external commands, deletion, or financial operations are mentioned.
Documented attack patterns abuse exactly the kind of access diagnose_local_layer 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 diagnose_local_layer:
{
"version": "1",
"default": "deny",
"tools": {
"diagnose_local_layer": {}
}
}diagnose_local_layer 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.
Diagnose local layer (project overrides) path and content issues. Use when local layers fail to load or have 0 topics. 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 diagnose_local_layer: 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.
diagnose_local_layer 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 diagnose_local_layer 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 diagnose_local_layer. 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.
diagnose_local_layer 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.