propose_field_mapping · ComplyOS MCP: Risk & Policy

WHAT IT DOES

What propose_field_mapping does on ComplyOS

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

Field mapping in a compliance/LMS context likely involves configuring how data fields are associated or transformed—a reversible configuration change. Without a description, confidence is reduced, but this appears to be Write-category (configuration creation) rather than Execute or Destructive.

From the tool's definition Tool name 'propose_field_mapping' suggests creating or modifying field mappings in a compliance system. The empty description limits certainty, but 'propose' typically indicates creating new configuration data rather than executing arbitrary operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

propose_field_mapping Rate-limited

propose_field_mapping 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": {
    "propose_field_mapping": {
      "limits": [
        {
          "counter": "propose_field_mapping_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 propose_field_mapping

What does the propose_field_mapping tool do? +

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

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

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

Can I rate-limit propose_field_mapping? +

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

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

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