record_attestation · ComplyOS MCP: Risk & Policy

WHAT IT DOES

What record_attestation does on ComplyOS

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

Attestations are records that document compliance statements or verification claims. Recording (creating/modifying) such records is a Write operation—reversible data creation in a compliance system. Severity is medium because attestations affect compliance documentation but are not destructive (records can be amended) and not financial.

From the tool's definition Tool name 'record_attestation' indicates creation/modification of attestation records. Context shows ComplyOS is a compliance auditing engine where attestations are formal compliance declarations. No description provided, limiting confidence.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

record_attestation Rate-limited

record_attestation 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": {
    "record_attestation": {
      "limits": [
        {
          "counter": "record_attestation_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 record_attestation

What does the record_attestation tool do? +

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

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

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

Can I rate-limit record_attestation? +

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

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

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