patent_assignee_search
Find patent assignees (companies / organizations) by name fragment. Returns assignee id, organization name, location, and total patents owned. Ranked by patent count.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/patent-assignee-search.md
What patent_assignee_search does on Livedatalink
AI agents call patent_assignee_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). |
organization | string | Yes | Company or organization name fragment (e.g. 'Apple', 'Genentech'). |
Parameters from the server's own tool schema.
Why patent_assignee_search is rated Low
This tool searches a patent database and returns read-only information about patent assignees. It performs a search operation that retrieves existing data without any side effects, modifications, or reversible changes. There is no evidence of write, execute, destructive, or financial capabilities. The low severity reflects that misuse would only expose publicly available patent information, with minimal blast radius.
From the tool's definition Tool description states it "Find[s] patent assignees" and "Returns assignee id, organization name, location, and total patents owned." These are query/retrieval operations with no modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs patent_assignee_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_assignee_search, this is the rule to start with:
patent_assignee_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_assignee_search call is checked against it from then on.
Questions about patent_assignee_search
Find patent assignees (companies / organizations) by name fragment. Returns assignee id, organization name, location, and total patents owned. Ranked by patent count. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
patent_assignee_search accepts 2 parameters: limit, organization. Required: organization. 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_assignee_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_assignee_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_assignee_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_assignee_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_assignee_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