AI agents call search_citations 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 searches patent citation data, which is a read-only query operation. No side effects are indicated. Even though the description is empty, the naming convention, server purpose, and sibling tool patterns strongly indicate this retrieves data without creating, modifying, or deleting information. Confidence is slightly reduced due to the missing tool description.
From the tool's definition Tool name 'search_citations' indicates a search operation. The server's stated purpose is to enable 'search, retrieval, and analysis of patents, PTAB proceedings, and litigation data.' Sibling tools include 'get_citation_metrics', 'get_enriched_citations',…
Documented attack patterns abuse exactly the kind of access search_citations 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_citations:
{
"version": "1",
"default": "deny",
"tools": {
"search_citations": {}
}
}search_citations 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.
search_citations. 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 search_citations: 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.
search_citations 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 search_citations 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 search_citations. 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.
search_citations 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.