list_taxonomy
Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventions (pillar/spoke, discriminant home, bicycle-guide-serves-all) as machine-readable data rather than prose.
This record as markdown: /tools/com-aiengineerprofessional-guide-registry/list-taxonomy.md
What list_taxonomy does on Guide Registry
AI agents call list_taxonomy to retrieve information from Guide Registry without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why list_taxonomy is rated Low
Even though list_taxonomy only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs list_taxonomy safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Guide Registry, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_taxonomy, this is the rule to start with:
list_taxonomy is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Guide Registry, apply this rule, and every list_taxonomy call is checked against it from then on.
Questions about list_taxonomy
Get the bicycle.guide vocabulary — domains, shelves (with live guide counts), series, personas, guide_types, and the classification conventions (pillar/spoke, discriminant home, bicycle-guide-serves-all) as machine-readable data rather than prose. It is categorised as a Read tool in the Guide Registry MCP Server, which means it retrieves data without modifying state.
Register the Guide Registry MCP server in PolicyLayer and add a rule for list_taxonomy: 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 Guide Registry. Nothing to install.
list_taxonomy 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_taxonomy 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_taxonomy. 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_taxonomy is provided by the Guide Registry MCP server (https://aiengineerprofessional.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Guide Registry, and thousands of servers like it.
This server
Across the catalogue