read_binary_download_chunk
Read one base64 chunk from a large PDF download returned by a Sanka PDF download tool. Concatenate chunks in offset order, then decode the combined base64 string.
This record as markdown: /tools/sankahq-sanka-mcp/read-binary-download-chunk.md
What read_binary_download_chunk does on Sanka MCP Server
AI agents call read_binary_download_chunk to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why read_binary_download_chunk is rated Low
This tool retrieves and decodes chunks of an already-initiated PDF download. It has no side effects, does not modify data, and only processes data that was previously requested. The operation is purely data retrieval, fitting the 'Read' category.
From the tool's definition Tool name explicitly contains 'read'; description states it 'Read[s] one base64 chunk' from a PDF download and requires manual concatenation and decoding. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
The rule that runs read_binary_download_chunk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_binary_download_chunk, this is the rule to start with:
read_binary_download_chunk 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 Sanka MCP Server, apply this rule, and every read_binary_download_chunk call is checked against it from then on.
Questions about read_binary_download_chunk
Read one base64 chunk from a large PDF download returned by a Sanka PDF download tool. Concatenate chunks in offset order, then decode the combined base64 string. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for read_binary_download_chunk: 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 Sanka MCP Server. Nothing to install.
read_binary_download_chunk 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_binary_download_chunk 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_binary_download_chunk. 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_binary_download_chunk is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue