Retrieve the full content of a file or specific chunks. Reads files directly from the filesystem. When to use this tool: - Get complete file content after finding files through search - Read documentation, code files, or configuration files for analysis - Extract specific sections of large files ...
AI agents call get_content to retrieve information from Directory Indexer without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_content performs pure data retrieval with no side effects. It reads and returns file content from the filesystem without creating, modifying, deleting, or executing anything. This is a canonical Read operation. The presence of sibling tools like 'delete_index' and 'index' confirms that destructive/write operations are implemented separately.
From the tool's definition Tool description states it 'Retrieve[s] the full content of a file' and 'Reads files directly from the filesystem'.
Risk signalsBulk/mass operation — affects multiple targets
Documented attack patterns abuse exactly the kind of access get_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Directory Indexer, and nothing reaches the server without passing your rules. This is the rule we recommend for get_content:
{
"version": "1",
"default": "deny",
"tools": {
"get_content": {}
}
}get_content is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Retrieve the full content of a file or specific chunks. Reads files directly from the filesystem. When to use this tool: - Get complete file content after finding files through search - Read documentation, code files, or configuration files for analysis - Extract specific sections of large files using chunk ranges - Access any text-based file content How it works: - Reads files directly from filesystem (not from search index) - Returns entire file by default - Can return specific chunk ranges for indexed files - Preserves original formatting and content Examples: - Get full file: file_path=. It is categorised as a Read tool in the Directory Indexer MCP Server, which means it retrieves data without modifying state.
Register the Directory Indexer MCP server in PolicyLayer and add a rule for get_content: 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 Directory Indexer. Nothing to install.
get_content 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_content 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_content. 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_content is provided by the Directory Indexer MCP server (peteretelej/directory-indexer). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Directory Indexer, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Directory Indexer tools catalogued and risk-classified — across an index of 43,000+ MCP servers.