[通用 Amazon 抓取 — 高级逃生口] 抓 5 个专用工具覆盖不到的页面。两种喂法二选一: ① content=裸零件(关键词/nodeId/sellerId/ASIN)+ site,后端按 parserName 自动拼基础 URL。content 模式不带筛选/排序/翻页 —— 只是裸零件。用户/AI 通常只有零件,简单页用这个最省事。 ② url=完整 Amazon 链接,任何筛选/排序/翻页都拼进这个 url(content 模式做不到的全靠它)。筛选语法举例:价格 $25-50 → '/s?k=earbuds&low-price=25&high-price=50';按评论数...
Risk signalsAccepts raw HTML/template content (content) · Accepts URL/endpoint input (url)
Part of the Amazon Mcp server.
Free to start. No card required.
AI agents call scrape_url 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 scrape_url 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": {
"scrape_url": {}
}
}See the full Amazon Mcp policy for all 20 tools.
These attack patterns abuse exactly the kind of access scrape_url 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 抓取 — 高级逃生口] 抓 5 个专用工具覆盖不到的页面。两种喂法二选一: ① content=裸零件(关键词/nodeId/sellerId/ASIN)+ site,后端按 parserName 自动拼基础 URL。content 模式不带筛选/排序/翻页 —— 只是裸零件。用户/AI 通常只有零件,简单页用这个最省事。 ② url=完整 Amazon 链接,任何筛选/排序/翻页都拼进这个 url(content 模式做不到的全靠它)。筛选语法举例:价格 $25-50 → '/s?k=earbuds&low-price=25&high-price=50';按评论数排序 → '&s=review-rank';翻页 → '&page=2';类目+价格 → '/s?i=aps&rh=n%3A172282&fs=true&low-price=25'。 Use when: 普通工具拼不出目标 URL —— "搜 X 但只要 $25-50""按评论排序的结果""类目按价格筛";或用户已有一个具体 Amazon 链接要抓。要带筛选就走 url 模式。 Don't use: 能用专用工具就别用 —— 纯关键词搜索用 search_amazon、单 ASIN 用 get_amazon_product、卖家用 list_seller_products、类目榜单用 list_bestsellers/list_new_releases。 Returns (format='json'): data.json[0].data.{ ... results[] ... },结构随 parserName 而定。⚠️ content/url 与 parserName 不匹配 → 后端返回 data.{ status_code, rawHtml, url }(未解析)。 Pair with: ↓ 拿到 asin 喂 get_amazon_product / get_amazon_reviews。 Cost: ~1 积点/次, ~5s。 ⚠️ content 和 url 二选一(都传或都不传会报错);带筛选/翻页必须用 url 模式;parserName 必须和页面类型匹配。. 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 scrape_url: 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.
scrape_url 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 scrape_url 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 scrape_url. 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.
scrape_url 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.