adaptercloud_sync_get

Fetch a single sync run by ID, including its counts and summary.

SERVERAdaptercloud SOURCE@burdenoff/adaptercloud-mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/burdenoff-adaptercloud-mcp/adaptercloud-sync-get.md

WHAT IT DOES

What adaptercloud_sync_get does on Adaptercloud

AI agents call adaptercloud_sync_get to retrieve information from Adaptercloud without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`id`	string	Yes	Sync run ID

Parameters from the server's own tool schema.

RISK

Why adaptercloud_sync_get is rated Low

Even though adaptercloud_sync_get only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adaptercloud_sync_get 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_get, this is the rule to start with:

adaptercloud_sync_get Allowed

adaptercloud_sync_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adaptercloud_sync_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adaptercloud, apply this rule, and every adaptercloud_sync_get call is checked against it from then on.

FAQ

Questions about adaptercloud_sync_get

What does the adaptercloud_sync_get tool do? +

Fetch a single sync run by ID, including its counts and summary. It is categorised as a Read tool in the Adaptercloud MCP Server, which means it retrieves data without modifying state.

What parameters does adaptercloud_sync_get accept? +

adaptercloud_sync_get accepts 1 parameter: id. Required: id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on adaptercloud_sync_get? +

Register the Adaptercloud MCP server in PolicyLayer and add a rule for adaptercloud_sync_get: 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.

What risk level is adaptercloud_sync_get? +

adaptercloud_sync_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adaptercloud_sync_get? +

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

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

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

KEEP EXPLORING

More on Adaptercloud, and thousands of servers like it.

This server

All 396 Adaptercloud tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_file_snippet on ACE-MCP →get_torrent_detail on M-Team MCP Server →get_customer_data on 08-AI-Business-Agent → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →