sync_sandbox_data
Copy a sample of production records into an active sandbox: per selected object, the newest 5,000 records with custom field values, line items, and associations between copied records. Additive and idempotent (re-running adds newer records without duplicating). Responds 202; progress lands in the...
This record as markdown: /tools/sankahq-sanka-mcp/sync-sandbox-data.md
What sync_sandbox_data does on Sanka MCP Server
AI agents use sync_sandbox_data to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why sync_sandbox_data is rated Medium
This tool writes production data into a sandbox environment, creating new records with custom field values, line items, and associations. It is additive (creates data) but not destructive (does not delete or overwrite).
From the tool's definition Copy a sample of production records into an active sandbox... Additive and idempotent (re-running adds newer records without duplicating)
Attacks that exploit this kind of access
The rule that runs sync_sandbox_data safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sync_sandbox_data, this is the rule to start with:
sync_sandbox_data 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 Sanka MCP Server, apply this rule, and every sync_sandbox_data call is checked against it from then on.
Questions about sync_sandbox_data
Copy a sample of production records into an active sandbox: per selected object, the newest 5,000 records with custom field values, line items, and associations between copied records. Additive and idempotent (re-running adds newer records without duplicating). Responds 202; progress lands in the sandbox copy_stats. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for sync_sandbox_data: 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 Sanka MCP Server. Nothing to install.
sync_sandbox_data 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 sync_sandbox_data 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 sync_sandbox_data. 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.
sync_sandbox_data is provided by the Sanka MCP Server MCP server (sankahq/sanka-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue