patent_landscape_async
Async extended variant of patent_landscape. Supports max_results up to 200 (vs 50 in sync mode) and an optional include_citation_graph flag that enriches each patent with its 2-level citation graph (parent patents that cite this one + child patents cited by this one). Returns immediately (<300ms)...
This record as markdown: /tools/io-github-getgapup-mcp-knowledge/patent-landscape-async.md
What patent_landscape_async does on Mcp Knowledge
AI agents call patent_landscape_async to retrieve information from Mcp Knowledge 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 |
|---|---|---|---|
mode | string | — | search / landscape / lookup. Default: "search" |
query | string | Yes | Keywords, company/inventor name, or patent number (e.g. "machine learning", "Tesla Inc") |
date_to | string | — | ISO date YYYY-MM-DD — latest filing date |
date_from | string | — | ISO date YYYY-MM-DD — earliest filing date |
max_results | number | — | Max patents to return (5-200). Default: 20 |
jurisdictions | array | — | Jurisdictions to include. Default: ["US","EP","WO"] |
include_citation_graph | boolean | — | If true, enriches each patent with a 2-level citation graph (parents + children). Adds significant processing time — use for deep analysis only. Default: false. |
Parameters from the server's own tool schema.
Why patent_landscape_async is rated Low
This tool retrieves and analyzes patent data including citation graphs and portfolio information. It is fundamentally a read/query operation — it returns patent landscape information asynchronously but does not create, modify, delete, or execute anything.
From the tool's definition patent landscape, deep R&D white-space analysis, freedom-to-operate (FTO) audits, VC due diligence IP mapping, large-scale competitor portfolio analysis, enriches each patent with its 2-level citation graph
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs patent_landscape_async safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Knowledge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patent_landscape_async, this is the rule to start with:
patent_landscape_async 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 Mcp Knowledge, apply this rule, and every patent_landscape_async call is checked against it from then on.
Questions about patent_landscape_async
Async extended variant of patent_landscape. Supports max_results up to 200 (vs 50 in sync mode) and an optional include_citation_graph flag that enriches each patent with its 2-level citation graph (parent patents that cite this one + child patents cited by this one). Returns immediately (<300ms) with a job_id. Poll the result with patent_landscape_result(job_id) after eta_seconds (~180s). Use for deep R&D white-space analysis, freedom-to-operate (FTO) audits, VC due diligence IP mapping, or large-scale competitor portfolio analysis. Async tool — register a webhook via webhooks_manage(register, url, [job.completed]) to receive callbacks instead of polling. Faster + lighter. It is categorised as a Read tool in the Mcp Knowledge MCP Server, which means it retrieves data without modifying state.
patent_landscape_async accepts 7 parameters: mode, query, date_to, date_from, max_results, jurisdictions, include_citation_graph. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Mcp Knowledge MCP server in PolicyLayer and add a rule for patent_landscape_async: 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 Mcp Knowledge. Nothing to install.
patent_landscape_async 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_landscape_async 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_landscape_async. 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_landscape_async is provided by the Mcp Knowledge MCP server (https://mcp.gapup.io). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Knowledge, and thousands of servers like it.
This server
Across the catalogue