AI agents call tts_doctor to retrieve information from Tts without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves and returns diagnostic information (auth status, profile settings, playback state) without modifying any data or triggering external operations. Pure read/query operation with minimal blast radius.
From the tool's definition Return auth/profile/playback diagnostics for the active TTS profile
Attacks that exploit this kind of access
Return auth/profile/playback diagnostics for the active TTS profile. It is categorised as a Read tool in the Tts MCP Server, which means it retrieves data without modifying state.
Register the Tts MCP server in PolicyLayer and add a rule for tts_doctor: 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 Tts. Nothing to install.
tts_doctor 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 tts_doctor 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 tts_doctor. 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.
tts_doctor is provided by the Tts MCP server (that-lucas/tts-mcp). 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 →