Merge one or more branch insights into a synthesis, best-evidence path, or decision note.
AI agents use ultrabrain_merge to create or update resources in Ultrabrain — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ultrabrain environment.
This tool creates or updates synthesized reasoning outputs by merging existing branch insights. While it modifies state within the reasoning system, it is reversible (can be undone via ultrabrain_reset or re-branching), and poses no destructive or external execution risk.
From the tool's definition Tool performs 'Merge...into a synthesis' which creates or modifies reasoning artifacts by combining branch insights into a consolidated output.
Attacks that exploit this kind of access
Merge one or more branch insights into a synthesis, best-evidence path, or decision note. It is categorised as a Write tool in the Ultrabrain MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ultrabrain MCP server in PolicyLayer and add a rule for ultrabrain_merge: 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 Ultrabrain. Nothing to install.
ultrabrain_merge 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 ultrabrain_merge 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 ultrabrain_merge. 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.
ultrabrain_merge is provided by the Ultrabrain MCP server (lcv-ideas-software/ultrabrain-mcp). 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 →