// MCP TOOL REFERENCE

transcribe_delete

Soft-delete a Scriptivox transcription record. Idempotent. Returns 409 CONFLICT if the job is still in-flight — cancel first via transcribe_cancel. Requires a configured API key.

ServerScriptivox
CategoryDestructive

How to control transcribe_delete ↓

WHAT IT DOES

What transcribe_delete does on Scriptivox

AI agents call transcribe_delete to permanently remove resources in Scriptivox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

THE RISK

Critical Risk

Why transcribe_delete needs a policy

Although described as 'soft-delete' (which typically means logical deletion rather than physical erasure), the tool irreversibly removes access to transcription data from the user's perspective and cannot be undone via this tool's API. The action results in permanent loss of the transcription record. This qualifies as Destructive rather than Write because deletion is not reversible.

From the tool's definition Soft-delete a Scriptivox transcription record. The verb 'delete' combined with the irreversible removal of data (transcription records) matches the Destructive category definition.

Documented attack patterns abuse exactly the kind of access transcribe_delete gives an agent:

POLICY

How to control transcribe_delete

PolicyLayer is an MCP gateway — it sits between your AI agents and Scriptivox, and nothing reaches the server without passing your rules. This is the rule we recommend for transcribe_delete:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "transcribe_delete"
  ]
}

transcribe_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Scriptivox — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Scriptivox tools

Destructive transcribe_cancel Cancel an in-flight Scriptivox transcription and release any reserved balance. Idempotent. Execute transcribe_url Transcribe audio or video from a public URL using Scriptivox AI. Supports 119 languages, s Execute transcription_url [DEPRECATED — use transcribe_url instead] Alias kept for backward compatibility with @scri Write transcribe_upload Transcribe a LOCAL file by uploading it to Scriptivox. Drives the 3-step upload flow inter Read check_balance Check your Scriptivox API credit balance, available hours, and pricing. Requires a configu Read get_api_docs Get Scriptivox API documentation. Sections: quickstart, transcribe, result, list, cancel, Read get_pricing Get Scriptivox pricing information including subscription plans (Free, Pro, Team) and API Read get_product_info Get information about Scriptivox capabilities: transcription, audio tools, video tools, su

All 14 Scriptivox tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Scriptivox → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about transcribe_delete

What does the transcribe_delete tool do? +

Soft-delete a Scriptivox transcription record. Idempotent. Returns 409 CONFLICT if the job is still in-flight — cancel first via transcribe_cancel. Requires a configured API key. It is categorised as a Destructive tool in the Scriptivox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on transcribe_delete? +

Register the Scriptivox MCP server in PolicyLayer and add a rule for transcribe_delete: 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 Scriptivox. Nothing to install.

What risk level is transcribe_delete? +

transcribe_delete is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit transcribe_delete? +

Yes. Add a rate_limit block to the transcribe_delete 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.

How do I block transcribe_delete completely? +

Set action: deny in the PolicyLayer policy for transcribe_delete. 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.

What MCP server provides transcribe_delete? +

transcribe_delete is provided by the Scriptivox MCP server (oci:docker.io/sparkleofficialmain/scriptivox-mcp-server:1.1.3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Scriptivox tool call.

Start from Scriptivox, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

14 Scriptivox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.