stream_project_snapshot_archive_endpoint
Stream Archive With Studio Project Audio. Spends ElevenLabs credits. Returns application/x-zip bytes; pass output_path to save them.
This record as markdown: /tools/aiwerk-mcp-server-elevenlabs/stream-project-snapshot-archive-endpoint.md
What stream_project_snapshot_archive_endpoint does on Elevenlabs
AI agents call stream_project_snapshot_archive_endpoint to retrieve information from Elevenlabs 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 |
|---|---|---|---|
project_id | string | Yes | The ID of the Studio project. |
output_path | string | — | Where to write the returned bytes. Relative paths resolve against ELEVENLABS_OUTPUT_DIR. Omit it to get the data inline as base64 (small files only). |
project_snapshot_id | string | Yes | The ID of the Studio project snapshot. |
Parameters from the server's own tool schema.
Why stream_project_snapshot_archive_endpoint is rated Low
Even though stream_project_snapshot_archive_endpoint only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs stream_project_snapshot_archive_endpoint safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elevenlabs, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For stream_project_snapshot_archive_endpoint, this is the rule to start with:
stream_project_snapshot_archive_endpoint 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 Elevenlabs, apply this rule, and every stream_project_snapshot_archive_endpoint call is checked against it from then on.
Questions about stream_project_snapshot_archive_endpoint
Stream Archive With Studio Project Audio. Spends ElevenLabs credits. Returns application/x-zip bytes; pass output_path to save them. It is categorised as a Read tool in the Elevenlabs MCP Server, which means it retrieves data without modifying state.
stream_project_snapshot_archive_endpoint accepts 3 parameters: project_id, output_path, project_snapshot_id. Required: project_id, project_snapshot_id. The full parameter table on this page comes from the server's own tool schema.
Register the Elevenlabs MCP server in PolicyLayer and add a rule for stream_project_snapshot_archive_endpoint: 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 Elevenlabs. Nothing to install.
stream_project_snapshot_archive_endpoint 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 stream_project_snapshot_archive_endpoint 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 stream_project_snapshot_archive_endpoint. 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.
stream_project_snapshot_archive_endpoint is provided by the Elevenlabs MCP server (@aiwerk/mcp-server-elevenlabs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elevenlabs, and thousands of servers like it.
This server
Across the catalogue