Low Risk

get_tts_speakers

get_tts_speakers

How to control get_tts_speakers ↓

AI agents call get_tts_speakers to retrieve information from PixVerse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

The naming convention 'get_' strongly indicates a read-only data retrieval operation. The tool appears to fetch speaker options or metadata for TTS functionality, which is a non-destructive query. Confidence is moderate (0.60) due to the empty description, but the 'get_' prefix is a reliable indicator of read operations. Low severity because retrieving metadata poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name 'get_tts_speakers' suggests retrieving a list or information about available text-to-speech speakers; no description provided to confirm.

Documented attack patterns abuse exactly the kind of access get_tts_speakers gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and PixVerse MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tts_speakers:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tts_speakers": {}
  }
}

get_tts_speakers is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register PixVerse MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_tts_speakers tool do? +

get_tts_speakers. It is categorised as a Read tool in the PixVerse MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tts_speakers? +

Register the PixVerse MCP server in PolicyLayer and add a rule for get_tts_speakers: 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 PixVerse MCP. Nothing to install.

What risk level is get_tts_speakers? +

get_tts_speakers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tts_speakers? +

Yes. Add a rate_limit block to the get_tts_speakers 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 get_tts_speakers completely? +

Set action: deny in the PolicyLayer policy for get_tts_speakers. 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 get_tts_speakers? +

get_tts_speakers is provided by the PixVerse MCP server (pixverseai/pixverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every PixVerse MCP tool call.

Deterministic rules across all 12 PixVerse MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

12 PixVerse MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.