Read a document from MarkLogic by URI
AI agents call read_document to retrieve information from MarkLogic 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 data from MarkLogic by its unique resource identifier (URI). It has no side effects, does not modify data, and does not execute code or external operations. It is a straightforward read operation that merely queries and returns existing document content.
From the tool's definition Tool name 'read_document' and description 'Read a document from MarkLogic by URI' clearly indicate document retrieval without modification. The verb 'Read' and lack of any mutating operations confirm this is a query operation.
Attacks that exploit this kind of access
Read a document from MarkLogic by URI. It is categorised as a Read tool in the MarkLogic MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MarkLogic MCP Server 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 MarkLogic MCP Server. 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 MarkLogic MCP Server MCP server (karthiknarayankotha/marklogic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →