Scans a folder for transcript files (.vtt, .srt, .txt, .md) and runs the full SDD auto-pipeline for each one. Designed for Power Automate + OneDrive workflows where meeting transcripts are saved automatically to a shared folder. Each transcript becomes its own feature spec package.
AI agents use sdd_batch_transcripts to create or update resources in Specky — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Specky environment.
This tool creates and writes new specification artifacts (requirements, architecture designs, task lists) based on input transcripts. While it processes existing files, its primary function is to generate new structured data outputs. It is Write rather than Execute because it does not run arbitrary code or shell commands—it follows a deterministic pipeline for specification generation.
From the tool's definition The tool 'scans a folder for transcript files' and 'runs the full SDD auto-pipeline for each one,' which generates and creates 'feature spec packages' from input transcripts.
Documented attack patterns abuse exactly the kind of access sdd_batch_transcripts gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Specky, and nothing reaches the server without passing your rules. This is the rule we recommend for sdd_batch_transcripts:
{
"version": "1",
"default": "deny",
"tools": {
"sdd_batch_transcripts": {
"limits": [
{
"counter": "sdd_batch_transcripts_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sdd_batch_transcripts 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.
Scans a folder for transcript files (.vtt, .srt, .txt, .md) and runs the full SDD auto-pipeline for each one. Designed for Power Automate + OneDrive workflows where meeting transcripts are saved automatically to a shared folder. Each transcript becomes its own feature spec package. It is categorised as a Write tool in the Specky MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Specky MCP server in PolicyLayer and add a rule for sdd_batch_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 Specky. Nothing to install.
sdd_batch_transcripts 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 sdd_batch_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 sdd_batch_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.
sdd_batch_transcripts is provided by the Specky MCP server (paulasilvatech/specky). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Specky, 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.
56 Specky tools catalogued and risk-classified — across an index of 43,000+ MCP servers.