Low Risk

check_pct_formalities

Check PCT formalities per Rules 5-12: abstract (Rule 8, <=150 words), description (Rule 5), claims (Rule 6), terminology (Rule 10, metric/Celsius), and physical requirements (Rule 11, A4/margins).

How to control check_pct_formalities ↓

AI agents call check_pct_formalities 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.

Low Risk

This tool retrieves or validates conformance of patent documents against regulatory requirements. It does not create, modify, delete, execute external code, or commit financial obligations. It is a read-only compliance verification function, consistent with the 'Read' category for tools that query or assess data without side effects.

From the tool's definition Tool name 'check_pct_formalities' and description indicate it performs validation checks against PCT Rules 5-12 standards.

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

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

check_pct_formalities 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 Claude Patent Creator — 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 check_pct_formalities tool do? +

Check PCT formalities per Rules 5-12: abstract (Rule 8, <=150 words), description (Rule 5), claims (Rule 6), terminology (Rule 10, metric/Celsius), and physical requirements (Rule 11, A4/margins). It is categorised as a Read tool in the Claude Patent Creator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_pct_formalities? +

Register the Claude Patent Creator MCP server in PolicyLayer and add a rule for check_pct_formalities: 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.

What risk level is check_pct_formalities? +

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

Can I rate-limit check_pct_formalities? +

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

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

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

Enforce policy on every Claude Patent Creator tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.