text_to_speech · Typecast API MCP Server MCP: Risk & Policy

WHAT IT DOES

What text_to_speech does on Typecast API MCP Server

AI agents invoke text_to_speech to trigger actions in Typecast API 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.

WHY IT NEEDS A POLICY

Why text_to_speech needs a policy

This tool initiates an external API call that performs a conversion operation (text to audio), which is an external execution/processing action rather than a simple data read or write. It consumes API credits/quota and produces a side-effect (audio generation) that depends on the arguments provided. Severity is medium as misuse could lead to quota exhaustion or generation of unwanted audio content.

From the tool's definition "Convert text to speech using the specified voice and parameters" — triggers an external text-to-speech conversion operation via the Typecast API

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

text_to_speech Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "text_to_speech": {
      "limits": [
        {
          "counter": "text_to_speech_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Typecast API MCP Server, so you can run agents against it safely.

FAQ

Questions about text_to_speech

What does the text_to_speech tool do? +

Convert text to speech using the specified voice and parameters. It is categorised as a Execute tool in the Typecast API MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on text_to_speech? +

Register the Typecast API MCP Server 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 Typecast API MCP Server. Nothing to install.

What risk level is text_to_speech? +

text_to_speech is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit text_to_speech? +

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.

How do I block text_to_speech completely? +

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.

What MCP server provides text_to_speech? +

text_to_speech is provided by the Typecast API MCP Server MCP server (neosapience/typecast-api-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.