Get chunks from a document with pagination. Use sparingly - prefer search or get_section for targeted retrieval.
AI agents call get_chunks to retrieve information from Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves documentation content segments. It performs data retrieval operations only, with no creation, modification, deletion, code execution, or financial implications. The pagination mechanism and advisory language confirm this is a safe read operation for accessing existing documentation content.
From the tool's definition Tool retrieves document chunks with pagination ('Get chunks from a document'); description explicitly advises to 'prefer search or get_section for targeted retrieval', indicating read-only data access with no side effects.
Attacks that exploit this kind of access
Get chunks from a document with pagination. Use sparingly - prefer search or get_section for targeted retrieval. It is categorised as a Read tool in the Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Documentation MCP Server MCP server in PolicyLayer and add a rule for get_chunks: 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 Documentation MCP Server. Nothing to install.
get_chunks 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_chunks 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_chunks. 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_chunks is provided by the Documentation MCP Server MCP server (wuyuwenj/api-doc-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 →