patent_inventor_search
Find inventors by last name (and optional first name). Returns inventor id, name, location, and total patent count. Use the inventor name in patent_search to find their patents.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/patent-inventor-search.md
What patent_inventor_search does on Livedatalink
AI agents call patent_inventor_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). |
last_name | string | Yes | Inventor last name (required). |
first_name | string | — | Optional inventor first name. |
Parameters from the server's own tool schema.
Why patent_inventor_search is rated Low
Even though patent_inventor_search only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs patent_inventor_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_inventor_search, this is the rule to start with:
patent_inventor_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_inventor_search call is checked against it from then on.
Questions about patent_inventor_search
Find inventors by last name (and optional first name). Returns inventor id, name, location, and total patent count. Use the inventor name in patent_search to find their patents. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
patent_inventor_search accepts 3 parameters: limit, last_name, first_name. Required: last_name. 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_inventor_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_inventor_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_inventor_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_inventor_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_inventor_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