AI agents use approve_ai_proposal 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.
The tool creates or modifies data (approves a proposal record) in a reversible manner. It does not delete data (Destructive), execute arbitrary code (Execute), or move money (Financial). While approval in a compliance context could have downstream consequences, the tool itself only mutates metadata and does not directly enforce compliance outcomes.
From the tool's definition Tool description states "Mutating metadata only: approve an AI proposal record" — this is a create/modify operation (approve/mutating) that changes data state, though explicitly limited to metadata without affecting "compliance truth".
Attacks that exploit this kind of access
Mutating metadata only: approve an AI proposal record without changing compliance truth. 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.
Register the ComplyOS MCP server in PolicyLayer and add a rule for approve_ai_proposal: 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.
approve_ai_proposal is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the approve_ai_proposal 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.
Set action: deny in the PolicyLayer policy for approve_ai_proposal. 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.
approve_ai_proposal 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →