patent_recent
List the most recently granted US patents since a start date (defaults to 30 days ago), newest first. Useful for monitoring newly issued patents.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/patent-recent.md
What patent_recent does on Livedatalink
AI agents invoke patent_recent to trigger actions in Livedatalink. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
start_date | string | — | Grant-date lower bound (YYYY-MM-DD). Defaults to 30 days ago. |
Parameters from the server's own tool schema.
Why patent_recent is rated High
patent_recent triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs patent_recent 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_recent, this is the rule to start with:
patent_recent stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_recent call is checked against it from then on.
Questions about patent_recent
List the most recently granted US patents since a start date (defaults to 30 days ago), newest first. Useful for monitoring newly issued patents. It is categorised as a Execute tool in the Livedatalink MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
patent_recent accepts 2 parameters: limit, 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_recent: 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_recent is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the patent_recent 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_recent. 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_recent 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.
Across the catalogue