Low Risk

get_related_docs

Find related documentation files based on metadata

How to control get_related_docs ↓

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

Low Risk

This tool performs a search/lookup operation to retrieve related documentation based on metadata criteria. It has no side effects, does not execute code, and does not modify or delete data. It is purely informational retrieval, fitting the Read category for low blast radius if misused by an AI agent.

From the tool's definition 'Find related documentation files based on metadata' - the tool queries and retrieves existing documentation using metadata filtering. No modification, deletion, or execution occurs.

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

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

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

get_related_docs 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 Rtfm — 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 get_related_docs tool do? +

Find related documentation files based on metadata. It is categorised as a Read tool in the Mcp Rtfm MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_related_docs? +

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

What risk level is get_related_docs? +

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

Can I rate-limit get_related_docs? +

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

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

get_related_docs is provided by the Mcp Rtfm MCP server (ryanjoachim/mcp-rtfm). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Mcp Rtfm tool call.

Deterministic rules across all 11 Mcp Rtfm tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

11 Mcp Rtfm 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.