Get detailed diagnostics for all configured layers including load status, errors, and performance metrics.
AI agents call get_layer_diagnostics 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 queries and returns system diagnostic data without creating, modifying, deleting, or executing any operations. It is purely informational and suitable for monitoring and debugging purposes. Low severity due to the benign nature of diagnostic metadata exposure.
From the tool's definition Tool retrieves diagnostic information ('load status, errors, and performance metrics') from configured layers. The verb 'get' and the nature of diagnostics as read-only reporting confirm no data modification or side effects occur.
Documented attack patterns abuse exactly the kind of access get_layer_diagnostics 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 get_layer_diagnostics:
{
"version": "1",
"default": "deny",
"tools": {
"get_layer_diagnostics": {}
}
}get_layer_diagnostics 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 detailed diagnostics for all configured layers including load status, errors, and performance metrics. 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 get_layer_diagnostics: 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.
get_layer_diagnostics 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 get_layer_diagnostics 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 get_layer_diagnostics. 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.
get_layer_diagnostics 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.