patents.epo-biblio

Bibliographic record for a patent publication via EPO OPS: invention titles (multiple languages), applicants, inventors, IPC classifications, application number, and the abstract. Worldwide coverage by publication number (e.g. EP1000000, US6093011). Net-new vs US-only patents.detail.

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-biblio.md

WHAT IT DOES

What patents.epo-biblio does on Mcp

AI agents call patents.epo-biblio 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-biblio is rated Low

The tool retrieves read-only bibliographic metadata about patents (titles, inventors, applicants, classifications, abstracts) from the EPO OPS database. There are no side effects, modifications, deletions, or financial transactions. It is a pure data retrieval operation. Severity is low as misuse would only expose publicly available patent information.

From the tool's definition Bibliographic record for a patent publication via EPO OPS: invention titles, applicants, inventors, IPC classifications, application number, and the abstract

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs patents.epo-biblio 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-biblio, this is the rule to start with:

patents.epo-biblio Allowed

patents.epo-biblio 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-biblio": {}
  }
}

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-biblio call is checked against it from then on.

FAQ

Questions about patents.epo-biblio

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

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

Register the MCP server in PolicyLayer and add a rule for patents.epo-biblio: 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-biblio? +

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

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

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

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

patents.epo-biblio 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 →