Return a hierarchical map of the entire help center: every category → its sections → its article titles and IDs (no bodies). Use this to give an agent a holistic picture of what the help center covers, as a precursor to targeted retrieval. Result can be large (~hundreds of articles) — prefer sear...
AI agents call browse_taxonomy to retrieve information from Wealthsimple Help Center MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a data retrieval tool that queries and returns structured information about help center content without side effects. It reads from the public Zendesk API to surface metadata (categories, sections, titles, IDs) for navigation purposes. No write, execute, destructive, or financial operations are possible with this tool.
From the tool's definition Tool description states it returns a 'hierarchical map' of 'article titles and IDs (no bodies)' from the help center, with explicit instruction to 'prefer search_help_center for narrow queries.' Keywords indicate pure retrieval: 'Return,' 'browsing,' 'map…
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Return a hierarchical map of the entire help center: every category → its sections → its article titles and IDs (no bodies). Use this to give an agent a holistic picture of what the help center covers, as a precursor to targeted retrieval. Result can be large (~hundreds of articles) — prefer search_help_center for narrow queries. It is categorised as a Read tool in the Wealthsimple Help Center MCP MCP Server, which means it retrieves data without modifying state.
Register the Wealthsimple Help Center MCP server in PolicyLayer and add a rule for browse_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 Wealthsimple Help Center MCP. Nothing to install.
browse_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 browse_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 browse_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.
browse_taxonomy is provided by the Wealthsimple Help Center MCP server (tatianathevisionary/wealthsimple-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →