Low Risk

search_litigation

search_litigation

How to control search_litigation ↓

AI agents call search_litigation to retrieve information from USPTO Patent MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Search operations retrieve and query data without modifying, deleting, or executing code. Litigation data search is informational lookup only, consistent with other sibling 'get_*' tools on the server. No destructive, financial, or execution capability indicated.

From the tool's definition Tool name 'search_litigation' and server context indicate querying/retrieval of litigation data. Sibling tools like 'get_litigation_case', 'get_party_litigation' and 'get_office_action_text' establish this server provides read-only access to USPTO patent data.

Documented attack patterns abuse exactly the kind of access search_litigation gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and USPTO Patent MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_litigation:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "search_litigation": {}
  }
}

search_litigation is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register USPTO Patent MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the search_litigation tool do? +

search_litigation. It is categorised as a Read tool in the USPTO Patent MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on search_litigation? +

Register the USPTO Patent MCP Server MCP server in PolicyLayer and add a rule for search_litigation: 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 USPTO Patent MCP Server. Nothing to install.

What risk level is search_litigation? +

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

Can I rate-limit search_litigation? +

Yes. Add a rate_limit block to the search_litigation 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 search_litigation completely? +

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

search_litigation is provided by the USPTO Patent MCP Server MCP server (riemannzeta/patent_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every USPTO Patent MCP Server tool call.

Deterministic rules across all 61 USPTO Patent MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

61 USPTO Patent MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.