Low Risk

filter_categories

[Amazon 类目商业指标筛选] 按销量/GMS/搜索量/转化率/退货率/价格档位/竞品密度等数十维指标筛类目,或当作"类目详情"接口取单个类目全量指标。 Use when: 用户说"找一些值得做的类目""筛销量大的类目""退货率低的类目""高搜索量但竞品少的类目""看看 X 类目(categoryId)的全部指标";类目层面的蓝海挖掘;要某个类目的 30+ 商业指标快照。 Don't use: 想筛细分 niche 而非整类目(用 filter_niches,颗粒度更细);想看类目下的具体商品(用 list_category_products);只想要类目名字(用 get_categ...

Risk signalsHigh parameter count (20 properties)

Part of the Amazon Mcp server.

filter_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 filter_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 filter_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": {
    "filter_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 filter_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 filter_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 filter_categories tool do? +

[Amazon 类目商业指标筛选] 按销量/GMS/搜索量/转化率/退货率/价格档位/竞品密度等数十维指标筛类目,或当作"类目详情"接口取单个类目全量指标。 Use when: 用户说"找一些值得做的类目""筛销量大的类目""退货率低的类目""高搜索量但竞品少的类目""看看 X 类目(categoryId)的全部指标";类目层面的蓝海挖掘;要某个类目的 30+ 商业指标快照。 Don't use: 想筛细分 niche 而非整类目(用 filter_niches,颗粒度更细);想看类目下的具体商品(用 list_category_products);只想要类目名字(用 get_category_paths)。 Returns: data.items.data[{ id, categoryId, marketplaceId, timeRange, sampleScope, snapshotDate, unitSoldSum, glanceViewsSum, searchVolumeSum, netShippedGmsSum, buyBoxPriceAvg, buyBoxPriceTier, searchToPurchaseRatio, returnRatio, asinCount, offersPerAsin, newAsinCount, newBrandCount, avgAdSpendPerClick, unitSoldTrendDirection, unitSoldChangeRateBucket, ... 趋势 + 分位数桶等数十字段 }] + data.items.pagination.{ total, page, size, hasNext }。翻页: 用 page 参数(默认 1,从 1 开始,size 上限 10);pagination.hasNext=true 表示还有下一页,hasNext=false 表示已到底。 Pair with: ↑ 必填 timeRange (常用 'l7d') + sampleScope ('all_asin') + marketplaceId(默认 US);categoryId 来自 search_categories / get_category_children;↓ 出来的高潜类目喂 list_category_products / list_bestsellers 看真实商品。 Cost: ~1 积点/页, ~5s。 Tips: size 上限 10(后端硬限制);翻页只在用户明确要"看更多候选类目"时才做,单次详情/快速筛选首页够用;长尾筛选字段(unitSoldTrendDirections / metricChangeRateBuckets 等数十个)走 extraFilters 透传。. 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 filter_categories? +

Register the Amazon MCP server in PolicyLayer and add a rule for filter_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 filter_categories? +

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

Can I rate-limit filter_categories? +

Yes. Add a rate_limit block to the filter_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 filter_categories completely? +

Set action: deny in the PolicyLayer policy for filter_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 filter_categories? +

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