List all 10 design directions
AI agents call list_directions 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 retrieves and returns a static list of design directions. It has no side effects, does not create or modify data, does not execute code, and does not involve financial transactions. It is a straightforward read operation typical of configuration or metadata retrieval in a design system.
From the tool's definition Tool name is 'list_directions' and description states 'List all 10 design directions' — a pure enumeration/retrieval operation with no modification, deletion, or execution of external operations.
Documented attack patterns abuse exactly the kind of access list_directions 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 list_directions:
{
"version": "1",
"default": "deny",
"tools": {
"list_directions": {}
}
}list_directions 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.
List all 10 design directions. 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 list_directions: 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.
list_directions 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 list_directions 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 list_directions. 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.
list_directions 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.