AI agents call ppubs_get_patent_by_number 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.
This tool retrieves patent records by number from the USPTO database. Retrieval operations have no side effects—they query and return existing data. The tool has a standard 'get' verb pattern indicating a read operation. No write, execution, or destructive capabilities are evident. Severity is low as misuse would only expose publicly available patent information.
From the tool's definition Tool name 'ppubs_get_patent_by_number' indicates retrieval of patent data by identifier. Context from sibling tools (get_citation_metrics, get_enriched_citations, get_office_action_text, get_litigation_case) shows this server provides query and retrieval…
Documented attack patterns abuse exactly the kind of access ppubs_get_patent_by_number 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 ppubs_get_patent_by_number:
{
"version": "1",
"default": "deny",
"tools": {
"ppubs_get_patent_by_number": {}
}
}ppubs_get_patent_by_number 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.
ppubs_get_patent_by_number. 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 ppubs_get_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 USPTO Patent MCP Server. Nothing to install.
ppubs_get_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 ppubs_get_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 ppubs_get_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.
ppubs_get_patent_by_number 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.