Low Risk

get_epub_metadata

Get metadata from an EPUB file.

How to control get_epub_metadata ↓

What get_epub_metadata does on MCP Document Reader

AI agents call get_epub_metadata to retrieve information from MCP Document Reader without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_epub_metadata needs a policy

This tool retrieves metadata (e.g., title, author, publication date) from an EPUB document. Metadata retrieval is a read-only operation that does not create, modify, delete, or execute any code. It has minimal blast radius if misused by an AI agent, as it only exposes informational properties of a document.

From the tool's definition Tool name is 'get_epub_metadata' and description states 'Get metadata from an EPUB file.' The verb 'get' and the word 'metadata' indicate retrieval of information without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_epub_metadata gives an agent:

How to control get_epub_metadata

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Document Reader, and nothing reaches the server without passing your rules. This is the rule we recommend for get_epub_metadata:

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

get_epub_metadata 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 MCP Document Reader — 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.

Related tools and policies

Go deeper

Questions about get_epub_metadata

What does the get_epub_metadata tool do? +

Get metadata from an EPUB file. It is categorised as a Read tool in the MCP Document Reader MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_epub_metadata? +

Register the MCP Document Reader MCP server in PolicyLayer and add a rule for get_epub_metadata: 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 Document Reader. Nothing to install.

What risk level is get_epub_metadata? +

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

Can I rate-limit get_epub_metadata? +

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

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

get_epub_metadata is provided by the MCP Document Reader MCP server (jbchouinard/mcp-document-reader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Document Reader tool call.

Start from MCP Document Reader, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

8 MCP Document Reader tools catalogued and risk-classified — across an index of 43,000+ 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.