Update which schemas/tables are enabled for a bulk sync.
AI agents use update_bulk_sync_schemas to create or update resources in Polytomic MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Polytomic MCP Server environment.
This tool creates or modifies data pipeline configuration reversibly. While it doesn't delete data, updating which schemas/tables are synced changes the behavior of automated data movement operations. The Write category applies because the modification is reversible—a user could update the schemas again to restore previous state.
From the tool's definition The tool name includes 'update' and the description states it modifies 'which schemas/tables are enabled for a bulk sync,' indicating it changes configuration of data synchronization pipelines.
Attacks that exploit this kind of access
Update which schemas/tables are enabled for a bulk sync. It is categorised as a Write tool in the Polytomic MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Polytomic MCP Server MCP server in PolicyLayer and add a rule for update_bulk_sync_schemas: 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.
update_bulk_sync_schemas 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 update_bulk_sync_schemas 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 update_bulk_sync_schemas. 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.
update_bulk_sync_schemas 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 →