Update the thinking bubble message
AI agents use private_thinking_delta 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 creates or modifies data (the thinking bubble message content) in a reversible manner. It is a write operation that updates display state without executing external code, deleting data, or causing financial impact. The scope is limited to UI message updates within the Claude Imagine interface.
From the tool's definition Tool name 'private_thinking_delta' and description 'Update the thinking bubble message' indicate modification of an existing UI message element within the visual builder.
Attacks that exploit this kind of access
Update the thinking bubble message. 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_thinking_delta: 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_thinking_delta 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_thinking_delta 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_thinking_delta. 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_thinking_delta 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 →