Use the Descript AI agent to trim or edit content in a project based on a prompt. Example: trim_transcript({ project_id:
AI agents use trim_transcript to create or update resources in Descript Complete — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Descript Complete environment.
This tool modifies transcript content reversibly (trim/edit operations can typically be undone in Descript). It is a Write operation because it creates or modifies data without irreversibly destroying it. Severity is medium because transcript modifications could impact project integrity or collaboration, but the effects are reversible.
From the tool's definition Tool is named 'trim_transcript' with description stating it will 'trim or edit content in a project based on a prompt.' The verb 'trim' and 'edit' indicate modification of existing transcript data.
Attacks that exploit this kind of access
Use the Descript AI agent to trim or edit content in a project based on a prompt. Example: trim_transcript({ project_id:. It is categorised as a Write tool in the Descript Complete MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Descript Complete MCP server in PolicyLayer and add a rule for trim_transcript: 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 Descript Complete. Nothing to install.
trim_transcript is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the trim_transcript 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 trim_transcript. 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.
trim_transcript is provided by the Descript Complete MCP server (josephtandle/descript-complete). 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 →