read_docs

SERVEREmailmd SOURCEemailmd

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/dev-emailmd-emailmd/read-docs.md

WHAT IT DOES

What read_docs does on Emailmd

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

Parameter	Type	Required	Description
`page`	string	—	Docs page path, e.g. 'buttons' or 'directives/hero'. Omit for the index.

Parameters from the server's own tool schema.

RISK

Why read_docs is rated Low

Tool retrieves documentation content with no side effects or data modification capabilities.

From the tool's definition Fetch emailmd documentation from emailmd.dev. Call with no arguments for the index of all pages

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs read_docs safely

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

read_docs Allowed

read_docs 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": {
    "read_docs": {}
  }
}

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

The button opens the PolicyLayer dashboard: create your workspace, connect Emailmd, apply this rule, and every read_docs call is checked against it from then on.

FAQ

Questions about read_docs

What does the read_docs tool do? +

Fetch emailmd documentation from emailmd.dev. Call with no arguments for the index of all pages; pass page to read one (e.g. 'buttons', 'frontmatter', 'theme', 'directives/hero'). Read the relevant page before using syntax you are not sure about. It is categorised as a Read tool in the Emailmd MCP Server, which means it retrieves data without modifying state.

What parameters does read_docs accept? +

read_docs accepts 1 parameter: page. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on read_docs? +

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

What risk level is read_docs? +

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

Can I rate-limit read_docs? +

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

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

read_docs is provided by the Emailmd MCP server (emailmd). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Emailmd, and thousands of servers like it.

This server

All 3 Emailmd tools →

Across the catalogue

claude_read_file on Claude Bridge →file_read on 0sec → The MCP Attack Database →

Guides

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