get_media_file
Retrieve one named Anki media file as base64 data and, for images, as MCP image content that compatible clients can inspect. Use this when an agent needs the actual contents of a referenced media asset, not when it only needs media names or storage operations; those belong in
This record as markdown: /tools/io-github-arielbk-anki-mcp/get-media-file.md
What get_media_file does on Anki
AI agents call get_media_file to retrieve information from Anki without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_media_file is rated Low
The tool retrieves and reads existing media files from Anki's storage. It does not modify, delete, execute, or move money. The action is non-destructive and has no side effects beyond returning the file contents. This is a straightforward Read operation.
From the tool's definition Tool description states it will 'Retrieve one named Anki media file as base64 data' - retrieval of data with no side effects on the media itself.
Attacks that exploit this kind of access
The rule that runs get_media_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Anki, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_media_file, this is the rule to start with:
get_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 Anki, apply this rule, and every get_media_file call is checked against it from then on.
Questions about get_media_file
Retrieve one named Anki media file as base64 data and, for images, as MCP image content that compatible clients can inspect. Use this when an agent needs the actual contents of a referenced media asset, not when it only needs media names or storage operations; those belong in. It is categorised as a Read tool in the Anki MCP Server, which means it retrieves data without modifying state.
Register the Anki MCP server in PolicyLayer and add a rule for get_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 Anki. Nothing to install.
get_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 get_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 get_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.
get_media_file is provided by the Anki MCP server (@arielbk/anki-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Anki, and thousands of servers like it.
This server
Across the catalogue