AI agents use merge_branch to create or update resources in Novyx — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Novyx environment.
Merging drafts constitutes creating/modifying data (combining multiple draft states into a unified state), fitting the Write category. Severity is medium because merge operations can cause conflicts or unintended data combinations, but effects are generally reversible through version control mechanisms typical in such governance systems.
From the tool's definition Tool description states 'Merge all open drafts in a branch/session' — merge operations modify data structures by combining branches, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access merge_branch gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Novyx, and nothing reaches the server without passing your rules. This is the rule we recommend for merge_branch:
{
"version": "1",
"default": "deny",
"tools": {
"merge_branch": {
"limits": [
{
"counter": "merge_branch_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}merge_branch 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.
Merge all open drafts in a branch/session. It is categorised as a Write tool in the Novyx MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Novyx MCP server in PolicyLayer and add a rule for merge_branch: 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 Novyx. Nothing to install.
merge_branch 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 merge_branch 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 merge_branch. 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.
merge_branch is provided by the Novyx MCP server (novyxlabs/novyx-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 120 Novyx tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
120 Novyx tools catalogued and risk-classified — across an index of 42,500+ MCP servers.