patent_details
Fetch full details for a single patent by its USPTO patent_id (e.g. '10757852'). Returns title, grant date, type, abstract, assignees, inventors, and citation count.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/patent-details.md
What patent_details does on Livedatalink
AI agents call patent_details 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 |
|---|---|---|---|
patent_id | string | Yes | USPTO patent id, e.g. '10757852'. |
Parameters from the server's own tool schema.
Why patent_details is rated Low
This tool performs a read-only lookup of publicly available patent information from the USPTO database. It retrieves structured metadata about a patent but does not create, modify, delete, or execute any operations. There is no financial transaction, code execution, or destructive action involved.
From the tool's definition Tool fetches and returns patent data (title, grant date, type, abstract, assignees, inventors, citation count) with no modification or deletion capability. The verb 'Fetch' and the output-only nature indicate data retrieval.
Attacks that exploit this kind of access
The rule that runs patent_details 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_details, this is the rule to start with:
patent_details 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_details call is checked against it from then on.
Questions about patent_details
Fetch full details for a single patent by its USPTO patent_id (e.g. '10757852'). Returns title, grant date, type, abstract, assignees, inventors, and citation count. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
patent_details accepts 1 parameter: patent_id. Required: patent_id. 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_details: 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_details 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_details 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_details. 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_details 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