workspace_resolve_conflict

What workspace_resolve_conflict does on Samarth Gtm Mcp

AI agents use workspace_resolve_conflict 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 workspace_resolve_conflict is rated Medium

Resolving a merge conflict modifies workspace data by selecting one version over another or creating a merged state. This is a reversible write operation (the previous conflict state can theoretically be recreated or undone via version control), not read-only. It does not delete data irreversibly or execute arbitrary code, so Write is the appropriate category.

From the tool's definition Tool name includes 'resolve_conflict' which indicates modification of workspace state. Description states 'Resolve a merge conflict for a workspace entity' — this modifies the state of the workspace by choosing a resolution path for conflicting versions.

The rule that runs workspace_resolve_conflict 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 workspace_resolve_conflict, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "workspace_resolve_conflict": {
      "limits": [
        {
          "counter": "workspace_resolve_conflict_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about workspace_resolve_conflict