Low Risk

search_categories

[Amazon 类目搜索] 用关键词(中英文均可)匹配 Amazon 类目树,返回候选类目节点。 Use when: 用户给的是关键词而非类目 ID,下游需要 categoryId / browseNodeId(如想跑 filter_niches / filter_categories / list_category_products / list_bestsellers slug 推测);想知道某个商品概念在 Amazon 类目体系里挂在哪。 Don't use: 已经有 categoryId/nodeId(直接用 get_category_paths 取面包屑或下游 filter);...

Part of the Amazon Mcp server.

search_categories is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE AMAZON MCP →

Free to start. No card required.

AI agents call search_categories 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 search_categories 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_categories": {}
  }
}

See the full Amazon Mcp policy for all 20 tools.

Get this rule live on your own Amazon Mcp server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY AMAZON MCP →

View all 20 tools →

These attack patterns abuse exactly the kind of access search_categories gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so search_categories only ever does what you allow.

SECURE AMAZON MCP →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the search_categories tool do? +

[Amazon 类目搜索] 用关键词(中英文均可)匹配 Amazon 类目树,返回候选类目节点。 Use when: 用户给的是关键词而非类目 ID,下游需要 categoryId / browseNodeId(如想跑 filter_niches / filter_categories / list_category_products / list_bestsellers slug 推测);想知道某个商品概念在 Amazon 类目体系里挂在哪。 Don't use: 已经有 categoryId/nodeId(直接用 get_category_paths 取面包屑或下游 filter);想树状下钻看子类目(用 get_category_children)。 Returns: data.items.data[{ browseNodeId, browseNodeIdPath, browseNodeName, browseNodeNameCn, browseNodeNamePath, browseNodeNamePathCn, parentBrowseNodeIdPath, productType, sellable, hasChild }] + pagination。 Pair with: ↓ 拿到 browseNodeId 后喂 list_category_products / list_bestsellers (用 path 推 slug) / filter_niches / filter_categories;↓ 喂 get_category_children 继续下钻;↓ 喂 get_category_paths 取面包屑。 Cost: ~1 积点/次, ~3s。. It is categorised as a Read tool in the Amazon Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_categories? +

Register the Amazon MCP server in PolicyLayer and add a rule for search_categories: 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.

What risk level is search_categories? +

search_categories is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit search_categories? +

Yes. Add a rate_limit block to the search_categories 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.

How do I block search_categories completely? +

Set action: deny in the PolicyLayer policy for search_categories. 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.

What MCP server provides search_categories? +

search_categories 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.

Enforce policy on every Amazon Mcp tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.