Diagnose weakest capability bottleneck
AI agents call learn_system_diagnose to retrieve information from BWVI without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs diagnostic analysis to identify system bottlenecks, which is fundamentally a read-only operation that retrieves or queries internal system state. It has no side effects on data or operations. The context of a design system (palette, typography, layout) reinforces that this is introspective analysis rather than any form of modification, execution, or destructive action.
From the tool's definition Tool name 'learn_system_diagnose' and description 'Diagnose weakest capability bottleneck' indicate analysis and retrieval of diagnostic information about system capabilities. No modification, deletion, code execution, or financial operations are indicated.
Documented attack patterns abuse exactly the kind of access learn_system_diagnose gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and BWVI, and nothing reaches the server without passing your rules. This is the rule we recommend for learn_system_diagnose:
{
"version": "1",
"default": "deny",
"tools": {
"learn_system_diagnose": {}
}
}learn_system_diagnose 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 weakest capability bottleneck. It is categorised as a Read tool in the BWVI MCP Server, which means it retrieves data without modifying state.
Register the BWVI MCP server in PolicyLayer and add a rule for learn_system_diagnose: 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 BWVI. Nothing to install.
learn_system_diagnose 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 learn_system_diagnose 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 learn_system_diagnose. 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.
learn_system_diagnose is provided by the BWVI MCP server (lh123aa/bwvi-design). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from BWVI, 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.
15 BWVI tools catalogued and risk-classified — across an index of 43,000+ MCP servers.