This record as markdown: /tools/adia-ai-mcp/get-chunk.md
What get_chunk does on Adia Ai
AI agents call get_chunk to retrieve information from Adia Ai without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_chunk is rated Low
The tool appears to retrieve a chunk of data from a file (likely JSON, CSV, or Excel based on server context). The description is empty, but the naming pattern and sibling tools strongly indicate a read-only operation that retrieves portions of data without modification. No mention of write, delete, or execution capabilities.
From the tool's definition Tool name 'get_chunk' combined with server description emphasizing 'reading, analyzing, and querying' and 'chunked processing for large datasets'. Sibling tools include 'get_json_chunk', 'query_json', 'read_excel', 'read_json' which are all read operations.
Attacks that exploit this kind of access
The rule that runs get_chunk safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adia Ai, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_chunk, this is the rule to start with:
get_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 Adia Ai, apply this rule, and every get_chunk call is checked against it from then on.
Questions about get_chunk
get_chunk is a read tool on the Adia Ai MCP server. It is categorised as a Read tool in the Adia Ai MCP Server, which means it retrieves data without modifying state.
Register the Adia Ai MCP server in PolicyLayer and add a rule for get_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 Adia Ai. Nothing to install.
get_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 get_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 get_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.
get_chunk is provided by the Adia Ai MCP server (@adia-ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adia Ai, and thousands of servers like it.
This server
Across the catalogue