Low Risk

get_status_code

get_status_code

How to control get_status_code ↓

AI agents call get_status_code 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

The tool name 'get_status_code' strongly implies reading or retrieving a status value without modifying data. Given the server's stated purpose of enabling 'search, retrieval, and analysis' and the absence of any destructive or write terminology, this is classified as Read.

From the tool's definition Tool name 'get_status_code' suggests retrieval of status information. No description provided, but the name pattern and context within USPTO Patent MCP Server (which provides 'access' and 'retrieval' of patent data) indicates a query/read operation.

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

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

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

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

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

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

Can I rate-limit get_status_code? +

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

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

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