[Amazon 类目树下钻] 从根节点或任意类目逐级下钻，列出直接子类目。 Use when: 用户说"看一下 Amazon 类目树""X 类目下有什么子类""列出顶级大类""下钻到三级类目"；做类目地图时；search_categories 给了多个候选类目想看哪个层级合适。 Don't use: 想按关键词跳到类目（用 search_categories 更快）；想要类目下的商品列表而非子类目（用 list_category_products）。 Returns: data.items.data[{ browseNodeId, browseNodeIdPath, browseNode...
Part of the Amazon Mcp server.
Free to start. No card required.
AI agents call get_category_children to retrieve information from Amazon Mcp without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_category_children only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_category_children": {}
}
}See the full Amazon Mcp policy for all 20 tools.
These attack patterns abuse exactly the kind of access get_category_children gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
[Amazon 类目树下钻] 从根节点或任意类目逐级下钻，列出直接子类目。 Use when: 用户说"看一下 Amazon 类目树""X 类目下有什么子类""列出顶级大类""下钻到三级类目"；做类目地图时；search_categories 给了多个候选类目想看哪个层级合适。 Don't use: 想按关键词跳到类目（用 search_categories 更快）；想要类目下的商品列表而非子类目（用 list_category_products）。 Returns: data.items.data[{ browseNodeId, browseNodeIdPath, browseNodeName, browseNodeNameCn, parentBrowseNodeIdPath, productType, sellable, hasChild }] + data.items.pagination.{ total, page, size, hasNext }；留空 parentBrowseNodeIdPath 返回顶级根节点；hasChild=1 说明可继续下钻。翻页: 用 page 参数（默认 1，size 默认 10、上限 50）；pagination.hasNext=true 表示该层子类目还没列完。 Pair with: ↑ 起点 parentBrowseNodeIdPath 可留空（顶级）或来自 search_categories；↓ 每条结果的 browseNodeIdPath 可喂回本工具再下钻一层，或喂 list_category_products / filter_categories。 Cost: ~1 积点/页, ~3s。翻页只在某节点子类目特别多（>size）且用户要"看全部子类"时才做。. It is categorised as a Read tool in the Amazon Mcp MCP Server, which means it retrieves data without modifying state.
Register the Amazon MCP server in PolicyLayer and add a rule for get_category_children: 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 Amazon Mcp. Nothing to install.
get_category_children 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_category_children 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_category_children. 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_category_children is provided by the Amazon MCP server (https://mcp.pangolinfo.com/mcp?api_key={api_key}). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 20 Amazon Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.