AI agents use promote_import_batch 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.
Based on the name alone, 'promote' suggests moving data to a higher environment or status, and 'import_batch' indicates bulk data ingestion. Within a compliance auditing system, this likely creates or modifies records (Write category). Without descriptive details, we cannot confirm if the operation is destructive or executes arbitrary code.
From the tool's definition Tool name 'promote_import_batch' indicates a reversible data modification operation (promote/import/batch). The empty description provides no additional context to assess whether this could be destructive or execute code.
Attacks that exploit this kind of access
promote_import_batch. 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 promote_import_batch: 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.
promote_import_batch 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 promote_import_batch 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 promote_import_batch. 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.
promote_import_batch 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 →