Get the full local file path for an audio file. Useful when you need to pass the audio file to another tool (like TTS voice cloning).
AI agents call get_audio_file_path to retrieve information from DMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves file path information without side effects. It reads/queries existing audio file data and returns a path string for use by other tools. No data is created, modified, deleted, or executed—it is purely informational retrieval, fitting the 'Read' category. Low severity because exposure of file paths has minimal blast radius in an RPG game context.
From the tool's definition Tool name 'get_audio_file_path' and description states it 'Get[s] the full local file path for an audio file' with no modification, deletion, or execution capability mentioned.
Documented attack patterns abuse exactly the kind of access get_audio_file_path gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_audio_file_path:
{
"version": "1",
"default": "deny",
"tools": {
"get_audio_file_path": {}
}
}get_audio_file_path 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.
Get the full local file path for an audio file. Useful when you need to pass the audio file to another tool (like TTS voice cloning). It is categorised as a Read tool in the DMCP MCP Server, which means it retrieves data without modifying state.
Register the D MCP server in PolicyLayer and add a rule for get_audio_file_path: 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 DMCP. Nothing to install.
get_audio_file_path 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_audio_file_path 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_audio_file_path. 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_audio_file_path is provided by the D MCP server (shawnrushefsky/dmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from DMCP, 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.
204 DMCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.