Lee el contenido de un archivo físicamente alojado en el disco local del host (Protegido por Sandbox contra .env)
AI agents call leer_archivo_local to retrieve information from Modular MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file content with no side effects. It is a straightforward read operation. The sandbox restriction on sensitive files (.env) and the read-only nature of the operation place it in the Read category with low severity, as the blast radius of misuse is confined to information disclosure of sandboxed local files.
From the tool's definition Tool name 'leer_archivo_local' means 'read_local_file'; description states 'reads the content of a file physically hosted on the local disk' (Lee el contenido). No modification, deletion, or execution occurs.
Attacks that exploit this kind of access
Lee el contenido de un archivo físicamente alojado en el disco local del host (Protegido por Sandbox contra .env). It is categorised as a Read tool in the Modular MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Modular MCP Server MCP server in PolicyLayer and add a rule for leer_archivo_local: 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 Modular MCP Server. Nothing to install.
leer_archivo_local 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 leer_archivo_local 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 leer_archivo_local. 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.
leer_archivo_local is provided by the Modular MCP Server MCP server (satanas66/tfm-mcp-062026). 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 →