patents.epo-legal

INPADOC legal-status events for a patent publication via EPO OPS: the timeline of procedural events (examination, grant, designations, national-phase entries, lapses, withdrawals) each with an event code, description, and date. For tracking whether a patent is in force, granted, or lapsed. Net-new.

SERVERMcp SOURCE@2sio/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-2s-io-mcp/patents.epo-legal.md

WHAT IT DOES

What patents.epo-legal does on Mcp

AI agents call patents.epo-legal to retrieve information from Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why patents.epo-legal is rated Low

This tool retrieves and queries historical legal-status data about patent events from the European Patent Office's OPS (Open Patent Services). It performs read-only lookups of procedural timelines and status information. The description explicitly frames this as 'for tracking' (information retrieval), with no indication of modifying, creating, deleting, or executing external actions.

From the tool's definition INPADOC legal-status events for a patent publication via EPO OPS: the timeline of procedural events (examination, grant, designations, national-phase entries, lapses, withdrawals) each with an event code, description, and date.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs patents.epo-legal safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For patents.epo-legal, this is the rule to start with:

patents.epo-legal Allowed

patents.epo-legal is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "patents.epo-legal": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcp, apply this rule, and every patents.epo-legal call is checked against it from then on.

FAQ

Questions about patents.epo-legal

What does the patents.epo-legal tool do? +

How do I enforce a policy on patents.epo-legal? +

Register the MCP server in PolicyLayer and add a rule for patents.epo-legal: 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 Mcp. Nothing to install.

What risk level is patents.epo-legal? +

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

Can I rate-limit patents.epo-legal? +

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

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

patents.epo-legal is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on , and thousands of servers like it.

This server

All 572 tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →