confirm_intake_scope · ComplyOS MCP: Risk & Policy

WHAT IT DOES

What confirm_intake_scope does on ComplyOS

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

WHY IT NEEDS A POLICY

Why confirm_intake_scope needs a policy

The tool appears to finalize or validate scope definitions within a compliance workflow, which is reversible data modification rather than destructive deletion or irreversible action. However, confidence is moderate (0.6) due to the empty description; if 'confirm' actually triggers an audit lock or freezes records in a way that prevents modification, severity and category could shift to Destructive.

From the tool's definition Tool name 'confirm_intake_scope' suggests locking in or committing scope parameters for a compliance intake process. The 'confirm' verb indicates a state-changing action.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

confirm_intake_scope Rate-limited

confirm_intake_scope 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.

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches ComplyOS, so you can run agents against it safely.

FAQ

Questions about confirm_intake_scope

What does the confirm_intake_scope tool do? +

confirm_intake_scope. It is categorised as a Write tool in the ComplyOS MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on confirm_intake_scope? +

Register the ComplyOS MCP server in PolicyLayer and add a rule for confirm_intake_scope: 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 ComplyOS. Nothing to install.

What risk level is confirm_intake_scope? +

confirm_intake_scope is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit confirm_intake_scope? +

Yes. Add a rate_limit block to the confirm_intake_scope 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.

How do I block confirm_intake_scope completely? +

Set action: deny in the PolicyLayer policy for confirm_intake_scope. 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.

What MCP server provides confirm_intake_scope? +

confirm_intake_scope is provided by the ComplyOS MCP server (simongonzalezdc/complyos). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.