dual_compliance_rule_create · DUAL MCP Server MCP

WHAT IT DOES

What dual_compliance_rule_create does on DUAL MCP Server

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

WHY IT NEEDS A POLICY

Why dual_compliance_rule_create needs a policy

Compliance rules are configuration data that, once created, govern future blockchain transactions and wallet behavior. This is a Write operation because compliance rules can be updated or deleted to reverse the change.

From the tool's definition Tool name and description indicate it 'Create[s] a new compliance rule' — a reversible modification of compliance settings that establish financial and operational guardrails (AML thresholds, transfer limits, restricted wallets, geographic restrictions).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

dual_compliance_rule_create Rate-limited

dual_compliance_rule_create 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": {
    "dual_compliance_rule_create": {
      "limits": [
        {
          "counter": "dual_compliance_rule_create_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 DUAL MCP Server, so you can run agents against it safely.

FAQ

Questions about dual_compliance_rule_create

What does the dual_compliance_rule_create tool do? +

Create a new compliance rule (AML threshold, transfer limit, restricted wallet, or geographic). It is categorised as a Write tool in the DUAL MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on dual_compliance_rule_create? +

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

What risk level is dual_compliance_rule_create? +

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

Can I rate-limit dual_compliance_rule_create? +

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

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

dual_compliance_rule_create is provided by the DUAL MCP Server MCP server (ro-ro-b/dual-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.