This record as markdown: /tools/io-github-davidmosiah-delx-mcp-server/util-merge-shallow.md
What util_merge_shallow does on Delx MCP Server
AI agents use util_merge_shallow to create or update resources in Delx MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Delx MCP Server environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
a | object | Yes | Input field: a. |
b | object | Yes | Input field: b. |
Parameters from the server's own tool schema.
Why util_merge_shallow is rated Medium
An AI agent can call util_merge_shallow faster than any human can review: one bad instruction and it creates or modifies resources in Delx MCP Server by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs util_merge_shallow safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Delx MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For util_merge_shallow, this is the rule to start with:
util_merge_shallow 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 Delx MCP Server, apply this rule, and every util_merge_shallow call is checked against it from then on.
Questions about util_merge_shallow
Shallow-merge two objects (b wins). It is categorised as a Write tool in the Delx MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
util_merge_shallow accepts 2 parameters: a, b. Required: a, b. The full parameter table on this page comes from the server's own tool schema.
Register the Delx MCP Server MCP server in PolicyLayer and add a rule for util_merge_shallow: 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 Delx MCP Server. Nothing to install.
util_merge_shallow 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 util_merge_shallow 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 util_merge_shallow. 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.
util_merge_shallow is provided by the Delx MCP Server MCP server (delx-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Delx MCP Server, and thousands of servers like it.
This server
Across the catalogue