read_media_file
Read a file and return it as a base64-encoded content block with its MIME type. Image and audio files are returned as image/audio content; any other file type is returned as an embedded resource. Only works within allowed directories.
This record as markdown: /tools/filesystem/read-media-file.md
What read_media_file does on Filesystem
AI agents call read_media_file to retrieve information from Filesystem without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes |
Parameters from the server's own tool schema.
Why read_media_file is rated Low
This tool retrieves and encodes file content for reading purposes only. It performs no modifications, deletions, or execution. The constraint to allowed directories further limits risk. This is a standard Read operation with low severity and high confidence.
From the tool's definition Tool name is 'read_media_file' and description states 'Read a file and return it as a base64-encoded content block'. The verb 'Read' combined with 'return' indicates data retrieval with no modification.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs read_media_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Filesystem, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For read_media_file, this is the rule to start with:
read_media_file 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 Filesystem, apply this rule, and every read_media_file call is checked against it from then on.
Questions about read_media_file
Read a file and return it as a base64-encoded content block with its MIME type. Image and audio files are returned as image/audio content; any other file type is returned as an embedded resource. Only works within allowed directories. It is categorised as a Read tool in the Filesystem MCP Server, which means it retrieves data without modifying state.
read_media_file accepts 1 parameter: path. Required: path. The full parameter table on this page comes from the server's own tool schema.
Register the Filesystem MCP server in PolicyLayer and add a rule for read_media_file: 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_media_file 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_media_file 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_media_file. 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_media_file is provided by the Filesystem MCP server (@modelcontextprotocol/server-filesystem). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Filesystem, and thousands of servers like it.
This server
Across the catalogue