This record as markdown: /tools/ruflo/results-merge.md
What results_merge does on Ruflo
AI agents use results_merge to create or update resources in Ruflo, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ruflo environment.
Why results_merge is rated Medium
This tool performs data merging using CRDT semantics, which modifies existing data structures in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), involve financial transactions (Financial), or merely retrieve data (Read).
From the tool's definition Tool name 'results_merge' and description 'Merge results with CRDT' indicate a data modification operation. CRDT (Conflict-free Replicated Data Type) merging is a write operation that combines/modifies data structures.
Attacks that exploit this kind of access
The rule that runs results_merge safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ruflo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For results_merge, this is the rule to start with:
results_merge 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Ruflo, apply this rule, and every results_merge call is checked against it from then on.
Questions about results_merge
Merge results with CRDT. It is categorised as a Write tool in the Ruflo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ruflo MCP server in PolicyLayer and add a rule for results_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 Ruflo. Nothing to install.
results_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 results_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 results_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.
results_merge is provided by the Ruflo MCP server (ruvnet/ruflo). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ruflo, and thousands of servers like it.
This server
Across the catalogue