AI agents invoke text_to_sound to trigger actions in Notify MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external text-to-speech operation that generates and likely stores/hosts an audio file, returning a link. This is more than a pure read—it executes a conversion process and produces an external artifact (hosted mp3). It spans Write/Execute; Execute is chosen as the most severe applicable category since it triggers an external operation whose result depends on the input text.
From the tool's definition 将一段文本转成mp3音频链接 (converts text to an mp3 audio link)
Documented attack patterns abuse exactly the kind of access text_to_sound gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Notify MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for text_to_sound:
{
"version": "1",
"default": "deny",
"tools": {
"text_to_sound": {
"limits": [
{
"counter": "text_to_sound_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}text_to_sound stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
将一段文本转成mp3音频链接. It is categorised as a Execute tool in the Notify MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Notify MCP Server MCP server in PolicyLayer and add a rule for text_to_sound: 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 Notify MCP Server. Nothing to install.
text_to_sound is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the text_to_sound 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 text_to_sound. 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.
text_to_sound is provided by the Notify MCP Server MCP server (oci:ghcr.io/aahl/mcp-notify:latest). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Notify MCP Server, 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.
21 Notify MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.