Get detailed information for a specific voice by ID using V2 API
AI agents call get_voice to retrieve information from Typecast API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries voice metadata by ID and returns information. It is purely a read operation that does not create, modify, delete, execute code, or perform financial transactions. The lack of side effects and straightforward retrieval nature places it firmly in the Read category with low severity.
From the tool's definition Tool description explicitly states 'Get detailed information for a specific voice by ID' — a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get detailed information for a specific voice by ID using V2 API. It is categorised as a Read tool in the Typecast API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Typecast API MCP Server MCP server in PolicyLayer and add a rule for get_voice: 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.
get_voice 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_voice 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_voice. 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_voice 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →