Fetch the transcript for a published Descript project by its share slug. Example: get_transcript({ slug:
AI agents call get_transcript to retrieve information from Descript Complete without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves transcription data from an existing published project. It performs a read-only query operation that does not create, modify, delete, or execute any operations. The only potential concern is unauthorized access to transcripts if share slugs are guessable or leaked, but that is a sensitivity issue of the data itself rather than a capability of the tool.
From the tool's definition Tool name is 'get_transcript' and description states 'Fetch the transcript for a published Descript project'. The verb 'Fetch' and 'Get' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
Fetch the transcript for a published Descript project by its share slug. Example: get_transcript({ slug:. It is categorised as a Read tool in the Descript Complete MCP Server, which means it retrieves data without modifying state.
Register the Descript Complete MCP server in PolicyLayer and add a rule for get_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.
get_transcript 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 get_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 get_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.
get_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 →