legal_fetch_patent_by_number
Fetch full patent details by patent number and jurisdiction. Read-only. No side effects. Idempotent. patent_number: Patent number in EPODOC format e.g. EP1000000 for European, CN120586032 for Chinese, JP2020123456 for Japanese, WO2020123456 for PCT, US10000000 for US. Required. jurisdiction: Opti...
This record as markdown: /tools/dev-7bd0-mcp-server/legal-fetch-patent-by-number.md
What legal_fetch_patent_by_number does on DataNexus MCP
AI agents call legal_fetch_patent_by_number to retrieve information from DataNexus MCP 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 |
|---|---|---|---|
jurisdiction | string | — | Patent office code: EP, US, WO. Default EP. Optional. |
patent_number | string | — | Patent number e.g. EP3456789 or US10123456. Required. |
Parameters from the server's own tool schema.
Why legal_fetch_patent_by_number is rated Low
This is a straightforward data retrieval operation against public patent databases. It queries existing information indexed by patent number and jurisdiction, returning structured patent metadata. No mutation, deletion, execution, or financial operations are possible. The read-only guarantee and idempotency explicitly stated in the description confirm zero side effects.
From the tool's definition Tool description explicitly states 'Read-only. No side effects. Idempotent.' The function fetches and retrieves patent details (title, abstract, inventors, assignees, filing date, claims, citations) without creating, modifying, deleting, or executing anything.
Attacks that exploit this kind of access
The rule that runs legal_fetch_patent_by_number safely
PolicyLayer is an MCP gateway: it sits between your AI agents and DataNexus MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For legal_fetch_patent_by_number, this is the rule to start with:
legal_fetch_patent_by_number 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 DataNexus MCP, apply this rule, and every legal_fetch_patent_by_number call is checked against it from then on.
Questions about legal_fetch_patent_by_number
Fetch full patent details by patent number and jurisdiction. Read-only. No side effects. Idempotent. patent_number: Patent number in EPODOC format e.g. EP1000000 for European, CN120586032 for Chinese, JP2020123456 for Japanese, WO2020123456 for PCT, US10000000 for US. Required. jurisdiction: Optional hint — one of EP, CN, JP, KR, US, WO, etc. Default EP. The tool normalises the patent number automatically; passing CN120586032 with jurisdiction EP is valid. Returns title, abstract, inventors, assignees, filing date, claims summary, and citation count. Use this when you have a specific patent number. Use legal_search_patents_by_keyword instead when you only have keywords and need to find patents. Verified source: EPO OPS. 24-hour cache. If this tool's response does not serve the user's need, call report_feedback with feedback_type="agent_gap", tool_id="legal_fetch_patent_by_number", intended_query="{what the user needed}", gap_description="{what was missing or wrong in the result}". It is categorised as a Read tool in the DataNexus MCP MCP Server, which means it retrieves data without modifying state.
legal_fetch_patent_by_number accepts 2 parameters: jurisdiction, patent_number. The full parameter table on this page comes from the server's own tool schema.
Register the DataNexus MCP server in PolicyLayer and add a rule for legal_fetch_patent_by_number: 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 DataNexus MCP. Nothing to install.
legal_fetch_patent_by_number 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 legal_fetch_patent_by_number 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 legal_fetch_patent_by_number. 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.
legal_fetch_patent_by_number is provided by the DataNexus MCP server (dev-7bd0/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on DataNexus, and thousands of servers like it.
This server
Across the catalogue