Get all voice reference clips for a specific character, along with character info. Returns file paths ready to use with voice cloning TTS engines.
AI agents call get_character_voice_references 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 queries and retrieves voice reference information for a character in the RPG system. It has no side effects, does not modify data, does not execute code or commands, and does not delete or overwrite anything. While it returns file paths usable with TTS engines, the tool itself only performs a read/retrieval operation.
From the tool's definition Tool description states 'Get all voice reference clips' and 'Returns file paths' — retrieves data without modifying game state or triggering external operations.
Documented attack patterns abuse exactly the kind of access get_character_voice_references 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_character_voice_references:
{
"version": "1",
"default": "deny",
"tools": {
"get_character_voice_references": {}
}
}get_character_voice_references 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 all voice reference clips for a specific character, along with character info. Returns file paths ready to use with voice cloning TTS engines. 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_character_voice_references: 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_character_voice_references 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_character_voice_references 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_character_voice_references. 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_character_voice_references 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.