Check USPTO API accessibility and API key validity.
AI agents call check_uspto_api_status to retrieve information from Claude Patent Creator without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only diagnostic check of API availability and key validity. It retrieves status information without creating, modifying, deleting, or executing any operations. No destructive, financial, or code execution effects are possible from a status check. Risk is low because misuse only reveals system state.
From the tool's definition Tool name contains 'check' and description states 'Check USPTO API accessibility and API key validity' — these are query/status operations with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access check_uspto_api_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Patent Creator, and nothing reaches the server without passing your rules. This is the rule we recommend for check_uspto_api_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_uspto_api_status": {}
}
}check_uspto_api_status 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.
Check USPTO API accessibility and API key validity. It is categorised as a Read tool in the Claude Patent Creator MCP Server, which means it retrieves data without modifying state.
Register the Claude Patent Creator MCP server in PolicyLayer and add a rule for check_uspto_api_status: 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 Claude Patent Creator. Nothing to install.
check_uspto_api_status 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 check_uspto_api_status 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 check_uspto_api_status. 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.
check_uspto_api_status is provided by the Claude Patent Creator MCP server (robthepcguy/claude-patent-creator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Claude Patent Creator tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
30 Claude Patent Creator tools catalogued and risk-classified — across an index of 42,500+ MCP servers.