adaptercloud_sync_complete
Mark a sync run as succeeded, recording its discovered/reconciled/drift/violation counts and a summary.
This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-sync-complete.md
What adaptercloud_sync_complete does on Adaptercloud
AI agents use adaptercloud_sync_complete to create or update resources in Adaptercloud, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Adaptercloud environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | Yes | Sync run ID |
summary | object | — | Run summary JSON |
driftCount | integer | — | Number of drift records detected |
violationCount | integer | — | Number of violations detected |
discoveredCount | integer | — | Number of resources discovered |
reconciledCount | integer | — | Number of resources reconciled |
Parameters from the server's own tool schema.
Why adaptercloud_sync_complete is rated Medium
An AI agent can call adaptercloud_sync_complete faster than any human can review: one bad instruction and it creates or modifies resources in Adaptercloud by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs adaptercloud_sync_complete safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adaptercloud, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adaptercloud_sync_complete, this is the rule to start with:
adaptercloud_sync_complete 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adaptercloud, apply this rule, and every adaptercloud_sync_complete call is checked against it from then on.
Questions about adaptercloud_sync_complete
Mark a sync run as succeeded, recording its discovered/reconciled/drift/violation counts and a summary. It is categorised as a Write tool in the Adaptercloud MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
adaptercloud_sync_complete accepts 6 parameters: id, summary, driftCount, violationCount, discoveredCount, reconciledCount. Required: id. The full parameter table on this page comes from the server's own tool schema.
Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_sync_complete: 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 Adaptercloud. Nothing to install.
adaptercloud_sync_complete 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 adaptercloud_sync_complete 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 adaptercloud_sync_complete. 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.
adaptercloud_sync_complete is provided by the Adaptercloud MCP server (@burdenoff/adaptercloud-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adaptercloud, and thousands of servers like it.
This server
Across the catalogue