Convert text to speech using various TTS engines. Can play audio directly or save to file.
AI agents invoke text_to_speech to trigger actions in A-Modular-Kingdom. 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 operation (TTS engine execution) and can either play audio directly on the system or write audio files to disk. The execution of external TTS engines and the ability to play audio or save files makes this an Execute-category tool. Misuse could involve playing unwanted audio, consuming system resources, or writing arbitrary audio files to disk.
From the tool's definition 'Convert text to speech using various TTS engines. Can play audio directly or save to file.'
Documented attack patterns abuse exactly the kind of access text_to_speech gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and A-Modular-Kingdom, and nothing reaches the server without passing your rules. This is the rule we recommend for text_to_speech:
{
"version": "1",
"default": "deny",
"tools": {
"text_to_speech": {
"limits": [
{
"counter": "text_to_speech_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} text_to_speech 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.
Convert text to speech using various TTS engines. Can play audio directly or save to file. It is categorised as a Execute tool in the A-Modular-Kingdom MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the A-Modular-Kingdom MCP server in PolicyLayer and add a rule for text_to_speech: 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 A-Modular-Kingdom. Nothing to install.
text_to_speech 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_speech 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_speech. 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_speech is provided by the A-Modular-Kingdom MCP server (masihmoafi/a-modular-kingdom). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from A-Modular-Kingdom, 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.
14 A-Modular-Kingdom tools catalogued and risk-classified — across an index of 43,000+ MCP servers.