containers_combine
[WRITE] Combine (merge) another container into this one.
This record as markdown: /tools/io-github-samarthanalytics-sj-samarth-gtm-mcp/containers-combine.md
What containers_combine does on Samarth Gtm Mcp
AI agents use containers_combine to create or update resources in Samarth Gtm Mcp, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Samarth Gtm Mcp environment.
Why containers_combine is rated Medium
The tool is explicitly tagged [WRITE] and performs a merge operation that modifies container configuration by combining another container into the current one. This is a reversible modification that alters data state but does not irreversibly delete.
From the tool's definition [WRITE] Combine (merge) another container into this one.
Attacks that exploit this kind of access
The rule that runs containers_combine safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Samarth Gtm Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For containers_combine, this is the rule to start with:
containers_combine 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 Samarth Gtm Mcp, apply this rule, and every containers_combine call is checked against it from then on.
Questions about containers_combine
[WRITE] Combine (merge) another container into this one. It is categorised as a Write tool in the Samarth Gtm Mcp MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Samarth Gtm MCP server in PolicyLayer and add a rule for containers_combine: 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 Samarth Gtm Mcp. Nothing to install.
containers_combine 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 containers_combine 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 containers_combine. 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.
containers_combine is provided by the Samarth Gtm MCP server (samarth-gtm-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Samarth Gtm, and thousands of servers like it.
This server
Across the catalogue