Get audio with base64 data included (for playback or processing)
AI agents call get_audio_data 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 and returns audio data in base64 format for consumption by the AI agent. It has no side effects on the game state or underlying data—it merely queries and returns existing audio. The blast radius of misuse is minimal: the agent could retrieve audio it shouldn't have access to (information disclosure), but cannot modify game state, execute commands, or cause irreversible damage.
From the tool's definition Tool name 'get_audio_data' and description 'Get audio with base64 data included (for playback or processing)' indicates retrieval of audio data without modification or deletion.
Documented attack patterns abuse exactly the kind of access get_audio_data 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_data:
{
"version": "1",
"default": "deny",
"tools": {
"get_audio_data": {}
}
}get_audio_data 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 audio with base64 data included (for playback or processing). 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_data: 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_data 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_data 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_data. 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_data 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.