assemblyai_list_transcripts
List recent AssemblyAI transcripts for the account.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/assemblyai-list-transcripts.md
What assemblyai_list_transcripts does on UnClick
AI agents call assemblyai_list_transcripts to retrieve information from UnClick 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 |
|---|---|---|---|
limit | number | — | Number of transcripts to return (default: 10, max: 200) |
status | string | — | Filter by status |
api_key | string | Yes | AssemblyAI API key |
after_id | string | — | Cursor: return transcripts after this ID |
before_id | string | — | Cursor: return transcripts before this ID |
Parameters from the server's own tool schema.
Why assemblyai_list_transcripts is rated Low
This tool queries and retrieves existing transcript data without creating, modifying, or deleting anything. It has no side effects beyond returning information. The blast radius of misuse is minimal — an attacker could view transcripts but cannot alter them, execute code, or cause financial harm.
From the tool's definition Tool name contains 'list' and description explicitly states 'List recent AssemblyAI transcripts for the account' — a retrieval operation with no modification or deletion.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs assemblyai_list_transcripts safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For assemblyai_list_transcripts, this is the rule to start with:
assemblyai_list_transcripts 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 UnClick, apply this rule, and every assemblyai_list_transcripts call is checked against it from then on.
Questions about assemblyai_list_transcripts
List recent AssemblyAI transcripts for the account. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
assemblyai_list_transcripts accepts 5 parameters: limit, status, api_key, after_id, before_id. Required: api_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for assemblyai_list_transcripts: 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 UnClick. Nothing to install.
assemblyai_list_transcripts 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 assemblyai_list_transcripts 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 assemblyai_list_transcripts. 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.
assemblyai_list_transcripts is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue