Read documentation content from the embedded Tenzir documentation.
AI agents call docs_read to retrieve information from Tenzir MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves documentation content, which is a read-only operation with no capability to modify data, execute code, delete resources, or perform financial transactions. The blast radius of misuse is minimal—an AI agent could only access available documentation. Therefore, it is classified as Read with low severity.
From the tool's definition Tool name 'docs_read' and description 'Read documentation content from the embedded Tenzir documentation' explicitly indicate retrieval of static documentation without modification or side effects.
Documented attack patterns abuse exactly the kind of access docs_read gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tenzir MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for docs_read:
{
"version": "1",
"default": "deny",
"tools": {
"docs_read": {}
}
}docs_read is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Read documentation content from the embedded Tenzir documentation. It is categorised as a Read tool in the Tenzir MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Tenzir MCP Server MCP server in PolicyLayer and add a rule for docs_read: 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 Tenzir MCP Server. Nothing to install.
docs_read 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 docs_read 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 docs_read. 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.
docs_read is provided by the Tenzir MCP Server MCP server (tenzir/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Tenzir MCP Server, 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.
15 Tenzir MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.