search_inventor
AI agents call search_inventor to retrieve information from USPTO Patent File Wrapper MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool appears to search for or retrieve inventor data from the USPTO Patent File Wrapper API without modifying, deleting, or executing any operations. Search operations are classified as Read category since they query data without side effects. Severity is low because retrieving patent inventor information from public USPTO records poses minimal risk of misuse.
From the tool's definition Tool name 'search_inventor' combined with sibling tools like 'search_applications' and 'search_applications_balanced' (which are clearly search/query operations) indicates this tool retrieves inventor information from USPTO records.
Attacks that exploit this kind of access
search_inventor. It is categorised as a Read tool in the USPTO Patent File Wrapper MCP Server MCP Server, which means it retrieves data without modifying state.
Register the USPTO Patent File Wrapper MCP Server MCP server in PolicyLayer and add a rule for search_inventor: 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 File Wrapper MCP Server. Nothing to install.
search_inventor 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_inventor 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_inventor. 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_inventor is provided by the USPTO Patent File Wrapper MCP Server MCP server (john-walkoe/uspto_pfw_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →