request_pvc_manual_verification
Request Manual Verification.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/request-pvc-manual-verification.md
What request_pvc_manual_verification does on Elevenlabs
AI agents call request_pvc_manual_verification to retrieve information from Elevenlabs without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
voice_id | string | Yes | Voice ID to be used, you can use https://api.elevenlabs.io/v1/voices to list all the available voices. |
extra_text | string | null | — | Extra text to be used in the manual verification process. |
files_paths | array | — | Verification documents Local paths. Required for this call. |
files_filenames | array | — | Filenames to send for "files". Some endpoints infer the audio format from them. |
files_base64_list | array | — | Base64 contents for "files", one entry per file. Use this when the server cannot read your local disk. |
Parameters from the server's own tool schema.
Why request_pvc_manual_verification is rated Low
Even though request_pvc_manual_verification only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs request_pvc_manual_verification safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For request_pvc_manual_verification, this is the rule to start with:
request_pvc_manual_verification is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Elevenlabs, apply this rule, and every request_pvc_manual_verification call is checked against it from then on.
Questions about request_pvc_manual_verification
Request Manual Verification. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
request_pvc_manual_verification accepts 5 parameters: voice_id, extra_text, files_paths, files_filenames, files_base64_list. Required: voice_id. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for request_pvc_manual_verification: 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 Elevenlabs. Nothing to install.
request_pvc_manual_verification 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 request_pvc_manual_verification 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 request_pvc_manual_verification. 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.
request_pvc_manual_verification is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue