Low Risk

patentsview_search_assignees

patentsview_search_assignees

How to control patentsview_search_assignees ↓

AI agents call patentsview_search_assignees 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

This tool searches USPTO patent assignee data, which is a read operation that retrieves public patent records without modifying, executing code, or affecting any data. The absence of a description is mitigated by the clear context from sibling tools and the overall server purpose. Low severity because unauthorized access to public patent records poses minimal risk.

From the tool's definition Tool name 'patentsview_search_assignees' combined with sibling tools (get_citation_metrics, get_cpc_info, get_enriched_citations, get_office_action_text) that are clearly retrieval-focused.

Documented attack patterns abuse exactly the kind of access patentsview_search_assignees 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 patentsview_search_assignees:

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

patentsview_search_assignees 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 patentsview_search_assignees tool do? +

patentsview_search_assignees. 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 patentsview_search_assignees? +

Register the USPTO Patent MCP Server MCP server in PolicyLayer and add a rule for patentsview_search_assignees: 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 patentsview_search_assignees? +

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

Can I rate-limit patentsview_search_assignees? +

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

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

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