patent_search
Search granted US patents by keyword (matched against title and abstract), title, and/or grant date range. Provide at least one of query, title, start_date, end_date. Returns title, grant date, assignee, and inventors.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/patent-search.md
What patent_search does on Livedatalink
AI agents call patent_search to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
query | string | — | Keyword(s) matched across patent title and abstract (e.g. 'lithium battery anode'). |
title | string | — | Keyword(s) matched against the patent title only. |
end_date | string | — | Grant-date upper bound (YYYY-MM-DD). |
start_date | string | — | Grant-date lower bound (YYYY-MM-DD). |
Parameters from the server's own tool schema.
Why patent_search is rated Low
patent_search retrieves publicly available patent information from the USPTO database. It performs a query-only operation that has no side effects, does not modify or delete data, does not execute code or external operations, and does not involve financial transactions. This is a straightforward Read category tool with low severity since misuse would only retrieve information already publicly available.
From the tool's definition Tool description explicitly states 'Search granted US patents' and 'Returns title, grant date, assignee, and inventors' — a pure data retrieval operation with no modification, deletion, or execution capability.
Attacks that exploit this kind of access
The rule that runs patent_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patent_search, this is the rule to start with:
patent_search is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every patent_search call is checked against it from then on.
Questions about patent_search
Search granted US patents by keyword (matched against title and abstract), title, and/or grant date range. Provide at least one of query, title, start_date, end_date. Returns title, grant date, assignee, and inventors. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
patent_search accepts 5 parameters: limit, query, title, end_date, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for patent_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 Livedatalink. Nothing to install.
patent_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 patent_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 patent_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.
patent_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue