bulk_set_duplicate_candidate_sla

What bulk_set_duplicate_candidate_sla does on Mapi Agent Memory

AI agents use bulk_set_duplicate_candidate_sla to create or update resources in Mapi Agent Memory, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mapi Agent Memory environment.

Why bulk_set_duplicate_candidate_sla is rated Medium

The 'set' operation indicates modification of SLA values for duplicate candidates. While reversible (hence Write rather than Destructive), bulk operations affecting SLAs in an audit/governance context poses medium-to-high risk if an agent misuses it with incorrect SLA assignments. High severity due to bulk scope; confidence reduced due to empty description.

From the tool's definition Tool name contains 'bulk_set' which indicates batch modification of data (SLA - Service Level Agreement records likely). The 'bulk' prefix suggests potential for high-volume side effects. Description is empty, limiting confidence.

Risk signalsBulk/mass operation — affects multiple targets

The rule that runs bulk_set_duplicate_candidate_sla safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mapi Agent Memory, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For bulk_set_duplicate_candidate_sla, this is the rule to start with:

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

Questions about bulk_set_duplicate_candidate_sla