AI agents call read_content to retrieve information from Filesystem without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves file contents without side effects. It performs a straightforward read operation consistent with the 'Read' category (retrieves or queries data; no side effects). The presence of sibling tools like delete_items, replace_content, and apply_diff on the same server does not change the classification of this specific tool.
From the tool's definition Tool name is 'read_content' and description states it 'Read[s] content from multiple specified files' with no mention of modification, deletion, or execution. This is a pure retrieval operation.
Documented attack patterns abuse exactly the kind of access read_content gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Filesystem, and nothing reaches the server without passing your rules. This is the rule we recommend for read_content:
{
"version": "1",
"default": "deny",
"tools": {
"read_content": {}
}
}read_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.
Read content from multiple specified files. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
Register the Filesystem MCP server in PolicyLayer and add a rule for read_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 Filesystem. Nothing to install.
read_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 read_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 read_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.
read_content is provided by the Filesystem MCP server (sylphxai/filesystem-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Filesystem, 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.
13 Filesystem tools catalogued and risk-classified — across an index of 43,000+ MCP servers.