Import an external transcript (e.g. from a transcription service) into the UI. Skips Whisper entirely. The transcript must include word-level timestamps.
AI agents use import_transcript to create or update resources in Podcli — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Podcli environment.
This tool modifies the application state by injecting external transcript data. While it doesn't execute code or delete data, it writes new information into the UI/system. An AI agent could import malformed, misleading, or adversarial transcripts that affect downstream clip generation, but the core action is data creation/modification rather than execution or destruction.
From the tool's definition Tool description states 'Import an external transcript... into the UI', which creates or inserts data into the system. The operation is reversible (transcripts can typically be deleted or replaced).
Documented attack patterns abuse exactly the kind of access import_transcript gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Podcli, and nothing reaches the server without passing your rules. This is the rule we recommend for import_transcript:
{
"version": "1",
"default": "deny",
"tools": {
"import_transcript": {
"limits": [
{
"counter": "import_transcript_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_transcript stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Import an external transcript (e.g. from a transcription service) into the UI. Skips Whisper entirely. The transcript must include word-level timestamps. It is categorised as a Write tool in the Podcli MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Podcli MCP server in PolicyLayer and add a rule for import_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 Podcli. Nothing to install.
import_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 import_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 import_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.
import_transcript is provided by the Podcli MCP server (nmbrthirteen/podcli). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Podcli, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
17 Podcli tools catalogued and risk-classified — across an index of 43,000+ MCP servers.