list_voices
AI agents call list_voices to retrieve information from PsyFlow-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list_' prefix strongly suggests a retrieval operation that queries available voices without modification or execution. Empty description lowers confidence slightly, but the name alone is sufficiently clear that this retrieves or enumerates data as a read-only operation. No side effects, no code execution, no data modification, and no destructive capability evident.
From the tool's definition Tool name 'list_voices' indicates a listing/enumeration operation. The description is empty, so judgment relies on the naming convention which follows standard read-operation patterns (list, get, fetch).
Attacks that exploit this kind of access
list_voices. It is categorised as a Read tool in the PsyFlow-MCP MCP Server, which means it retrieves data without modifying state.
Register the PsyFlow- MCP server in PolicyLayer and add a rule for list_voices: 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 PsyFlow-MCP. Nothing to install.
list_voices 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 list_voices 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 list_voices. 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.
list_voices is provided by the PsyFlow- MCP server (taskbeacon/taskbeacon-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 →