create_privacy_request · ComplyOS MCP: Risk & Policy

WHAT IT DOES

What create_privacy_request does on ComplyOS

AI agents use create_privacy_request 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 create_privacy_request needs a policy

The tool creates new privacy requests, which are reversible modifications to compliance state. This is a Write action rather than Execute (no code execution implied) or Destructive (privacy requests can typically be withdrawn or modified). High severity due to potential to create privacy obligations or audit trail entries that could affect enterprise compliance posture.

From the tool's definition Tool name is 'create_privacy_request' with empty description. The 'create_' prefix indicates data creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_privacy_request Rate-limited

create_privacy_request 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": {
    "create_privacy_request": {
      "limits": [
        {
          "counter": "create_privacy_request_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 create_privacy_request

What does the create_privacy_request tool do? +

create_privacy_request. 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 create_privacy_request? +

Register the ComplyOS MCP server in PolicyLayer and add a rule for create_privacy_request: 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 create_privacy_request? +

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

Can I rate-limit create_privacy_request? +

Yes. Add a rate_limit block to the create_privacy_request 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 create_privacy_request completely? +

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

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