Read various document formats (DOCX, DOC, TXT, MD, HTML, etc.)
AI agents call read_document to retrieve information from Doc Ops without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries document content without side effects. It performs a passive read operation across multiple document format types. No data is created, modified, deleted, or executed. The lowest severity is appropriate since document reading has minimal security impact unless the documents themselves contain highly sensitive information—but that is a data sensitivity issue, not a tool capability issue.
From the tool's definition Tool name 'read_document' and description explicitly states 'Read various document formats (DOCX, DOC, TXT, MD, HTML, etc.)' with no modification, deletion, or execution capability mentioned.
Documented attack patterns abuse exactly the kind of access read_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Doc Ops, and nothing reaches the server without passing your rules. This is the rule we recommend for read_document:
{
"version": "1",
"default": "deny",
"tools": {
"read_document": {}
}
}read_document 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 various document formats (DOCX, DOC, TXT, MD, HTML, etc.). It is categorised as a Read tool in the Doc Ops MCP Server, which means it retrieves data without modifying state.
Register the Doc Ops MCP server in PolicyLayer and add a rule for read_document: 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 Doc Ops. Nothing to install.
read_document 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 read_document 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 read_document. 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.
read_document is provided by the Doc Ops MCP server (tele-ai/doc-ops-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 13 Doc Ops tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
13 Doc Ops tools catalogued and risk-classified — across an index of 42,500+ MCP servers.