# adaptercloud_sync_fail

Mark a sync run as failed with an error message.

Agent View of the PolicyLayer registry record for `adaptercloud_sync_fail`. HTML page: https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-sync-fail

## Facts

- Tool: `adaptercloud_sync_fail`
- Server: Adaptercloud (`@burdenoff/adaptercloud-mcp`) — https://policylayer.com/tools/burdenoff-adaptercloud-mcp.md
- Install: `npx -y @burdenoff/adaptercloud-mcp`
- Homepage: https://www.npmjs.com/package/@burdenoff/adaptercloud-mcp
- Risk category: Execute (High risk)
- Registry record: grade F, identity unverified
- Server rate-limited: no
- Parameters: 2 (2 required)
- Recommended policy verdict: Rate-limited

## Parameters

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `id` | string | yes | Sync run ID |
| `error` | string | yes | Failure reason / error message |

Parameters from the server's own tool schema.

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "adaptercloud_sync_fail",
    "arguments": {
      "id": "<id>",
      "error": "<error>"
    }
  }
}
```

## Why adaptercloud_sync_fail is rated High

adaptercloud_sync_fail triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

## Use case

AI agents invoke adaptercloud_sync_fail to trigger actions in Adaptercloud. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

## Recommended policy (PolicyLayer)

Verdict: **Rate-limited**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Adaptercloud:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "adaptercloud_sync_fail": {
      "limits": [
        {
          "counter": "adaptercloud_sync_fail_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}
```

## Other tools on Adaptercloud (395)

- `adaptercloud_auth_logout` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-auth-logout.md
- `adaptercloud_billing_payment_methods_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-billing-payment-methods-remove.md
- `adaptercloud_billing_subscriptions_cancel` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-billing-subscriptions-cancel.md
- `adaptercloud_channels_connections_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-channels-connections-delete.md
- `adaptercloud_channels_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-channels-delete.md
- `adaptercloud_conversations_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-delete.md
- `adaptercloud_conversations_drafts_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-drafts-delete.md
- `adaptercloud_conversations_messages_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-messages-delete.md
- `adaptercloud_conversations_messages_unpin` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-messages-unpin.md
- `adaptercloud_conversations_participants_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-participants-remove.md
- `adaptercloud_conversations_reactions_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-conversations-reactions-remove.md
- `adaptercloud_devportal_api_keys_revoke` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-api-keys-revoke.md
- `adaptercloud_devportal_apps_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-apps-delete.md
- `adaptercloud_devportal_apps_webhooks_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-apps-webhooks-remove.md
- `adaptercloud_devportal_delegations_revoke` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-delegations-revoke.md
- `adaptercloud_devportal_oauth_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-oauth-delete.md
- `adaptercloud_devportal_orgs_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-devportal-orgs-delete.md
- `adaptercloud_files_revoke` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-files-revoke.md
- `adaptercloud_files_share_revoke` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-files-share-revoke.md
- `adaptercloud_groups_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-groups-delete.md
- `adaptercloud_groups_members_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-groups-members-remove.md
- `adaptercloud_integrations_connections_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-integrations-connections-delete.md
- `adaptercloud_integrations_connections_revoke` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-integrations-connections-revoke.md
- `adaptercloud_integrations_tags_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-integrations-tags-remove.md
- `adaptercloud_organizations_members_remove` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-organizations-members-remove.md
- `adaptercloud_products_content_pages_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-products-content-pages-delete.md
- `adaptercloud_products_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-products-delete.md
- `adaptercloud_products_feature_flags_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-products-feature-flags-delete.md
- `adaptercloud_products_shortcuts_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-products-shortcuts-delete.md
- `adaptercloud_rbac_roles_delete` — Destructive — https://policylayer.com/tools/burdenoff-adaptercloud-mcp/adaptercloud-rbac-roles-delete.md
- …and 365 more: https://policylayer.com/tools/burdenoff-adaptercloud-mcp.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=burdenoff-adaptercloud-mcp · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/burdenoff-adaptercloud-mcp