通常会話 ネコ用。
AI agents invoke speak_kurono_neko to trigger actions in PVV 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.
This tool triggers an external TTS (text-to-speech) operation via the VOICEVOX Web API for a specific speaker (Kurono Neko). It executes an external service call that produces audio output, making it an Execute category. The description '通常会話 ネコ用' (Normal conversation, for Neko) is minimal but consistent with sibling tools.
From the tool's definition Tool name 'speak_kurono_neko' and server description indicate text-to-speech synthesis using VOICEVOX Web API, triggering external audio generation operations
Attacks that exploit this kind of access
通常会話 ネコ用。. It is categorised as a Execute tool in the PVV MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the PVV MCP Server MCP server in PolicyLayer and add a rule for speak_kurono_neko: 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 PVV MCP Server. Nothing to install.
speak_kurono_neko is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the speak_kurono_neko 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 speak_kurono_neko. 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.
speak_kurono_neko is provided by the PVV MCP Server MCP server (lambda-tuber/pvv-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 →