AI agents call patentsview_get_assignee 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.
Assignee lookups are informational queries of patent metadata—specifically identifying who owns or holds a patent. This is a read-only operation with no capability to modify, delete, or execute arbitrary code. No financial transactions are involved. The low severity reflects that unauthorized access to publicly available or semi-public patent assignee data carries minimal risk.
From the tool's definition Tool name 'patentsview_get_assignee' indicates retrieval of assignee information from PatentsView database.
Documented attack patterns abuse exactly the kind of access patentsview_get_assignee 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_get_assignee:
{
"version": "1",
"default": "deny",
"tools": {
"patentsview_get_assignee": {}
}
}patentsview_get_assignee is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
patentsview_get_assignee. It is categorised as a Read tool in the USPTO Patent MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USPTO Patent MCP Server MCP server in PolicyLayer and add a rule for patentsview_get_assignee: 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.
patentsview_get_assignee 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 patentsview_get_assignee 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 patentsview_get_assignee. 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.
patentsview_get_assignee 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.
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.