legal_search_patents_by_keyword

SERVERDataNexus MCP SOURCEdev-7bd0/mcp-server

Low RISK CLASS

Category Read

Parameters 30 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/dev-7bd0-mcp-server/legal-search-patents-by-keyword.md

WHAT IT DOES

What legal_search_patents_by_keyword does on DataNexus MCP

AI agents call legal_search_patents_by_keyword 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
`keywords`	string	—	Search keyword or phrase e.g. CRISPR gene editing. Required.
`date_from`	string	—	Earliest filing date ISO 8601 e.g. 2020-01-31. Optional.
`jurisdiction`	string	—	Patent office code: EP, US, WO. Default EP. Optional.

Parameters from the server's own tool schema.

RISK

Why legal_search_patents_by_keyword is rated Low

This tool queries publicly available patent data and returns results without any capability to modify, delete, execute code, or trigger external operations. It is a pure read operation with no side effects, fitting the Read category. Severity is low because patent data is public and no damage can result from querying it.

From the tool's definition Tool description explicitly states 'Read-only. No side effects. Idempotent. Returns up to 10 matches.' The operation is a search that retrieves patent metadata (numbers, titles, filing dates) from public patent databases without modification or execution…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs legal_search_patents_by_keyword 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_search_patents_by_keyword, this is the rule to start with:

legal_search_patents_by_keyword Allowed

legal_search_patents_by_keyword is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "legal_search_patents_by_keyword": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect DataNexus MCP, apply this rule, and every legal_search_patents_by_keyword call is checked against it from then on.

FAQ

Questions about legal_search_patents_by_keyword

What does the legal_search_patents_by_keyword tool do? +

Search patents by keyword across EPO, USPTO, or WIPO. Read-only. No side effects. Idempotent. Returns up to 10 matches. keywords: Search terms describing the invention e.g. neural network image classification. Required. jurisdiction: One of EP, US, or WO. Optional. Default EP. date_from: Earliest filing date in ISO 8601 format e.g. 2020-01-31. Optional, defaults to no lower bound. Returns patent numbers, titles, and filing dates. Use this when finding prior art or exploring a technology landscape without a specific number. Use legal_fetch_patent_by_number instead when you have the patent number already. Verified source: EPO OPS + USPTO. 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_search_patents_by_keyword", 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.

What parameters does legal_search_patents_by_keyword accept? +

legal_search_patents_by_keyword accepts 3 parameters: keywords, date_from, jurisdiction. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on legal_search_patents_by_keyword? +

Register the DataNexus MCP server in PolicyLayer and add a rule for legal_search_patents_by_keyword: 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.

What risk level is legal_search_patents_by_keyword? +

legal_search_patents_by_keyword is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit legal_search_patents_by_keyword? +

Yes. Add a rate_limit block to the legal_search_patents_by_keyword 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.

How do I block legal_search_patents_by_keyword completely? +

Set action: deny in the PolicyLayer policy for legal_search_patents_by_keyword. 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.

What MCP server provides legal_search_patents_by_keyword? +

legal_search_patents_by_keyword 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.

KEEP EXPLORING

More on DataNexus, and thousands of servers like it.

This server

All 55 DataNexus tools →

Across the catalogue

keyword_search on Azure AI Agent Service + Azure AI Search MCP Server →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →