Fetches TTS instructions by calling get_voice_info.
AI agents call get_tts_instructions to retrieve information from MCP TTS Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs information retrieval without creating, modifying, deleting, or executing code. It accesses existing TTS instruction data through a subordinate call to get_voice_info. There is no indication of data mutation, code execution, or external operation triggering.
From the tool's definition The tool description explicitly states it 'Fetches TTS instructions', which indicates a retrieval operation.
Documented attack patterns abuse exactly the kind of access get_tts_instructions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP TTS Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tts_instructions:
{
"version": "1",
"default": "deny",
"tools": {
"get_tts_instructions": {}
}
}get_tts_instructions 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.
Fetches TTS instructions by calling get_voice_info. It is categorised as a Read tool in the MCP TTS Server MCP Server, which means it retrieves data without modifying state.
Register the MCP TTS Server MCP server in PolicyLayer and add a rule for get_tts_instructions: 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 MCP TTS Server. Nothing to install.
get_tts_instructions 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_tts_instructions 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_tts_instructions. 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_tts_instructions is provided by the MCP TTS Server MCP server (kristofferv98/mcp_tts_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP TTS 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.
4 MCP TTS Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.