End streaming and finalize HTML content
AI agents use private_streamable_end to create or update resources in Claude Imagine — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claude Imagine environment.
This tool concludes a streaming session and finalizes HTML content rendered in the browser. It is a Write operation as it commits/modifies displayed web interface content. It is not Destructive because finalization is a completion action (not deletion), though it may irreversibly end the stream. Severity is medium because misuse could corrupt or lock in unintended UI state, but it doesn't delete data or move money.
From the tool's definition 'End streaming and finalize HTML content' — finalizes/commits HTML content to the browser UI
Attacks that exploit this kind of access
End streaming and finalize HTML content. It is categorised as a Write tool in the Claude Imagine MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claude Imagine MCP server in PolicyLayer and add a rule for private_streamable_end: 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 Claude Imagine. Nothing to install.
private_streamable_end 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 private_streamable_end 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 private_streamable_end. 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.
private_streamable_end is provided by the Claude Imagine MCP server (t3rm1nu55/claudeimagine). 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 →