Retrieve a specific chunk by its ID. Use this to get full context for a search result.
AI agents call get_chunk to retrieve information from IndexFoundry MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pre-existing data (a specific chunk) from the vector database by its ID. There are no indications of creation, modification, deletion, or execution of arbitrary code. The operation is purely informational and has no side effects beyond returning data, placing it squarely in the Read category.
From the tool's definition Tool name is 'get_chunk' and description states 'Retrieve a specific chunk by its ID.' The verb 'retrieve' and the stated purpose to 'get full context' indicate a read-only data access operation with no modifications or side effects.
Attacks that exploit this kind of access
Retrieve a specific chunk by its ID. Use this to get full context for a search result. It is categorised as a Read tool in the IndexFoundry MCP MCP Server, which means it retrieves data without modifying state.
Register the IndexFoundry 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 IndexFoundry MCP. 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 IndexFoundry MCP server (mnehmos/mnehmos.index-foundry.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 →