get_doc
Fetch a single documentation page as Markdown, given a product id and a page slug (both come from list_products / search_docs results, or a doc URL like /liteship/overview). Returns the title, description, a heading outline, and the full Markdown body.
This record as markdown: /tools/com-freebatteryfactory-docs/get-doc.md
What get_doc does on Docs
AI agents call get_doc to retrieve information from Docs 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 |
|---|---|---|---|
slug | string | Yes | Page slug, e.g. "overview" or "factory" (from search_docs results or the last path segment of a doc URL). |
product | string | Yes | Product id from list_products (e.g. "liteship", "batpak"). |
Parameters from the server's own tool schema.
Why get_doc is rated Low
This tool retrieves and returns documentation content without creating, modifying, deleting, executing code, or affecting external systems. It is a pure read operation on static documentation pages, with no reversible or irreversible side effects. The minimal blast radius if misused is simply over-fetching documentation—no data corruption, system impact, or financial consequence.
From the tool's definition Tool description explicitly states it 'Fetch[es] a single documentation page' and 'Returns the title, description, a heading outline, and the full Markdown body.' The verb 'Fetch' and the read-only nature of retrieving static documentation content with no…
Attacks that exploit this kind of access
The rule that runs get_doc safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Docs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_doc, this is the rule to start with:
get_doc is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Docs, apply this rule, and every get_doc call is checked against it from then on.
Questions about get_doc
Fetch a single documentation page as Markdown, given a product id and a page slug (both come from list_products / search_docs results, or a doc URL like /liteship/overview). Returns the title, description, a heading outline, and the full Markdown body. It is categorised as a Read tool in the Docs MCP Server, which means it retrieves data without modifying state.
get_doc accepts 2 parameters: slug, product. Required: slug, product. The full parameter table on this page comes from the server's own tool schema.
Register the Docs MCP server in PolicyLayer and add a rule for get_doc: 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 Docs. Nothing to install.
get_doc is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_doc 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.
Set action: deny in the PolicyLayer policy for get_doc. 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.
get_doc is provided by the Docs MCP server (https://freebatteryfactory.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Docs, and thousands of servers like it.
This server
Across the catalogue