save_audio
AI agents use save_audio to create or update resources in Edge-TTS MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Edge-TTS MCP Server environment.
This tool creates or modifies audio files (a form of data creation), which fits the Write category. It is reversible—generated audio files can be deleted or overwritten. Severity is low because saving audio has minimal blast radius; the worst outcome is storage of unwanted audio files, which is not destructive, financial, or code-execution.
From the tool's definition Tool name 'save_audio' indicates writing/persisting audio data. Server context shows it generates audio files from text-to-speech synthesis. The sibling tool 'text_to_speech' and server capability to 'generate audio files' confirms this writes new media files.
Attacks that exploit this kind of access
save_audio. It is categorised as a Write tool in the Edge-TTS MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Edge-TTS MCP Server MCP server in PolicyLayer and add a rule for save_audio: 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 Edge-TTS MCP Server. Nothing to install.
save_audio is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the save_audio 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 save_audio. 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.
save_audio is provided by the Edge-TTS MCP Server MCP server (yangwuan55/edge-tts-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →