Low Risk

search_office_actions

search_office_actions

How to control search_office_actions ↓

AI agents call search_office_actions 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 performs a search query against USPTO office action records, which is fundamentally a read-only retrieval operation. No side effects, modifications, deletions, or executions are implied. The empty description slightly reduces confidence, but the naming pattern and server context strongly suggest a standard search/retrieval function consistent with the Read category.

From the tool's definition Tool name 'search_office_actions' combined with sibling tools like 'get_office_action_text', 'get_office_action_citations', and 'get_office_action_rejections' indicate this is a retrieval/search operation.

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

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

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

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

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

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

Can I rate-limit search_office_actions? +

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

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

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