書き起こしの状態一覧を取得します
AI agents call CHECK_TRANSCRIPTION_STATUSES to retrieve information from mocoVoice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current status of transcription jobs. It queries state information without creating, modifying, deleting, or executing any operations. The data returned is read-only metadata about previously initiated transcription processes. No side effects or irreversible actions are performed.
From the tool's definition Tool name contains 'CHECK' and description translates to 'Get a list of transcription statuses' — a retrieval operation. The verb 'get' and 'list' indicate querying existing data without modification.
Attacks that exploit this kind of access
書き起こしの状態一覧を取得します. It is categorised as a Read tool in the mocoVoice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the mocoVoice MCP Server MCP server in PolicyLayer and add a rule for CHECK_TRANSCRIPTION_STATUSES: 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 mocoVoice MCP Server. Nothing to install.
CHECK_TRANSCRIPTION_STATUSES 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 CHECK_TRANSCRIPTION_STATUSES 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 CHECK_TRANSCRIPTION_STATUSES. 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.
CHECK_TRANSCRIPTION_STATUSES is provided by the mocoVoice MCP Server MCP server (mocomoco-inc/mocovoice-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 →