[Amazon 类目面包屑解析] 批量把 categoryId 还原成完整路径（如 'Electronics > Headphones > Over-Ear Headphones'）。 Use when: 报告/分析里需要展示类目上下文（不是裸 ID）；用户只有一组数字 ID 想知道它们叫什么；多个类目对比时需要可读名字。 Don't use: 只有一个 ID 时其实用不上（其他 tool 返回里通常已带 browseNodeNamePath）；想看类目树结构（用 get_category_children）。 Returns: data.items[{ categoryId, cate...
Part of the Amazon Mcp server.
Free to start. No card required.
AI agents call get_category_paths 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_paths 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_paths": {}
}
}See the full Amazon Mcp policy for all 20 tools.
These attack patterns abuse exactly the kind of access get_category_paths 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 类目面包屑解析] 批量把 categoryId 还原成完整路径（如 'Electronics > Headphones > Over-Ear Headphones'）。 Use when: 报告/分析里需要展示类目上下文（不是裸 ID）；用户只有一组数字 ID 想知道它们叫什么；多个类目对比时需要可读名字。 Don't use: 只有一个 ID 时其实用不上（其他 tool 返回里通常已带 browseNodeNamePath）；想看类目树结构（用 get_category_children）。 Returns: data.items[{ categoryId, categoryName, categoryNameCn, browseNodeNamePaths[], browseNodeNamePathCns[] }] —— 输入数组多大就返回多大。 Pair with: ↑ categoryIds 从任何前一步拿（filter_niches/filter_categories 的输出、用户粘的 ID 列表）；↓ 主要给人看，下游链路通常不依赖。 Cost: ~1 积点/次, ~2s（批量解析比单调多次便宜）。. 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_paths: 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_paths 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_paths 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_paths. 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_paths 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.