text_to_speech · Android MCP Server MCP: Risk & Policy

WHAT IT DOES

What text_to_speech does on Android MCP Server

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

Text-to-speech causes the device to produce audible output, which is an external operation with real-world effects (sound output). It goes beyond read/write of data, as it actively triggers device hardware (speaker). It cannot be considered purely destructive or financial, but it executes a system-level action with potential for misuse (e.g., speaking unwanted content aloud, social engineering bystanders).

From the tool's definition Speak text aloud via TTS — triggers an external audio output operation on the Android device

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 Android MCP Server, so you can run agents against it safely.

FAQ

Questions about text_to_speech

What does the text_to_speech tool do? +

Speak text aloud via TTS. It is categorised as a Execute tool in the Android 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 Android 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 Android 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 Android MCP Server MCP server (wujie272/android-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.