[PACER 美国专利诉讼检索] 按专利号 / 公司名 / 法院案件号查美国联邦法院专利诉讼案件,返回案件档案 + 完整 docket 流水时间线。 Use when: 用户说"查美国专利诉讼""这个专利被起诉过吗""X 公司有没有专利官司""某案件号的进展""新品所用专利有没有诉讼史""IP 侵权风险排查(诉讼维度)";WIPO 查到风险专利号后,下一步定位对应的美国诉讼。 Don't use: 想查外观专利/商标本身(用 wipo_search);想查商品/评论/排名(这是诉讼库,不是商品库)。 Returns: data.data.{ total, hits[{ docketId,...
Part of the Amazon Mcp server.
Free to start. No card required.
AI agents call pacer_search 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 pacer_search 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": {
"pacer_search": {}
}
}See the full Amazon Mcp policy for all 20 tools.
These attack patterns abuse exactly the kind of access pacer_search 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.
[PACER 美国专利诉讼检索] 按专利号 / 公司名 / 法院案件号查美国联邦法院专利诉讼案件,返回案件档案 + 完整 docket 流水时间线。 Use when: 用户说"查美国专利诉讼""这个专利被起诉过吗""X 公司有没有专利官司""某案件号的进展""新品所用专利有没有诉讼史""IP 侵权风险排查(诉讼维度)";WIPO 查到风险专利号后,下一步定位对应的美国诉讼。 Don't use: 想查外观专利/商标本身(用 wipo_search);想查商品/评论/排名(这是诉讼库,不是商品库)。 Returns: data.data.{ total, hits[{ docketId, docketNumber, pacerCaseId, caseName, court, courtId, assignedTo, suitNature, jurisdiction, status, dateFiled, dateTerminated, parties[], patentNumbers[], entryTotal, entries[{ documentNumber, dateFiled, description, documentHref, pdfUrl, patentNumbers[], extraDocument[{ document_number, document_href, pdf_url, patent_sumbers[] }] }] }] }(双层 data 外壳,与 wipo_search 一致)。注意 entries[].extraDocument 是该诉讼事件下挂的附件列表,大多为空 [](全量仅约 0.014% entry 有附件);附件字段是 snake_case(与 entry 本身驼峰不同),且 patent_sumbers 是上游原始拼写(非 numbers)。 Pair with: ↑ patentNumber / companyName / caseNumber 至少一个,多个 AND 取交集;↑ 常接 wipo_search(先 WIPO 找风险专利号 → 再 pacer_search 定位诉讼);↓ entries[].pdfUrl 及 extraDocument[].pdf_url 可让用户下载原始法律文书/附件。 Cost: ~12 积点/次, ~3s。 ⚠️ 三个查询条件至少传一个,否则报错;size 上限 50,entrySize 上限 200;30s 超时则补更精确的专利号/案件号缩小范围。. 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 pacer_search: 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.
pacer_search 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 pacer_search 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 pacer_search. 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.
pacer_search 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.