Delete a bulk sync from Polytomic.
AI agents call delete_bulk_sync to permanently remove resources in Polytomic MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a bulk sync configuration, which cannot be undone. Bulk syncs are data pipeline orchestrations that may be critical to ongoing data operations. Deletion destroys the configuration and potentially disrupts dependent workflows. While it does not directly delete source or destination data, it irreversibly removes the sync definition itself, making it a Destructive action.
From the tool's definition Tool name 'delete_bulk_sync' combined with description 'Delete a bulk sync from Polytomic' indicates irreversible deletion of a bulk synchronization configuration.
Attacks that exploit this kind of access
Delete a bulk sync from Polytomic. It is categorised as a Destructive tool in the Polytomic MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Polytomic MCP Server MCP server in PolicyLayer and add a rule for delete_bulk_sync: 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 Polytomic MCP Server. Nothing to install.
delete_bulk_sync is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the delete_bulk_sync 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 delete_bulk_sync. 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.
delete_bulk_sync is provided by the Polytomic MCP Server MCP server (therevenueengineer/polytomic-mcp). 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 →