Synchronize the active workshared document with central. Only works with workshared (central model) documents. For non-workshared documents, use save_document instead. Args: comment: Sync comment visible in the worksharing log. compact: If True, compact the central model during sync. relinquish_a...
AI agents use sync_with_central to create or update resources in MCP server for Revit - Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP server for Revit - Python environment.
This tool pushes local changes to the central Revit model, making edits visible and persistent for all collaborators. It modifies shared project state but is a standard save/sync operation (not irreversible deletion), placing it in Write.
From the tool's definition Synchronize the active workshared document with central
Documented attack patterns abuse exactly the kind of access sync_with_central gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP server for Revit - Python, and nothing reaches the server without passing your rules. This is the rule we recommend for sync_with_central:
{
"version": "1",
"default": "deny",
"tools": {
"sync_with_central": {
"limits": [
{
"counter": "sync_with_central_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}sync_with_central 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.
Free to start. No card required.
Synchronize the active workshared document with central. Only works with workshared (central model) documents. For non-workshared documents, use save_document instead. Args: comment: Sync comment visible in the worksharing log. compact: If True, compact the central model during sync. relinquish_all: If True (default), relinquish all borrowed elements and worksets after sync. It is categorised as a Write tool in the MCP server for Revit - Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP server for Revit - Python MCP server in PolicyLayer and add a rule for sync_with_central: 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 MCP server for Revit - Python. Nothing to install.
sync_with_central 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_with_central 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_with_central. 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_with_central is provided by the MCP server for Revit - Python MCP server (mcp-servers-for-revit/mcp-server-for-revit-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP server for Revit - Python, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
20 MCP server for Revit - Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.