Rollback the current transaction to the point of transaction_begin.
AI agents use transaction_rollback to create or update resources in AutoCAD MCP Pro — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AutoCAD MCP Pro environment.
This tool reverts uncommitted changes within an active transaction—a core Write operation capability in CAD systems. It is categorized as Write rather than Destructive because: (1) it only rolls back the current transaction scope, not permanent deletion; (2) the changes being undone were not yet persisted; (3) this is a standard transactional control mechanism.
From the tool's definition Tool name 'transaction_rollback' and description indicate reversal of modifications within a transaction scope back to 'transaction_begin'.
Documented attack patterns abuse exactly the kind of access transaction_rollback gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AutoCAD MCP Pro, and nothing reaches the server without passing your rules. This is the rule we recommend for transaction_rollback:
{
"version": "1",
"default": "deny",
"tools": {
"transaction_rollback": {
"limits": [
{
"counter": "transaction_rollback_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} transaction_rollback 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.
Rollback the current transaction to the point of transaction_begin. It is categorised as a Write tool in the AutoCAD MCP Pro MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AutoCAD MCP Pro MCP server in PolicyLayer and add a rule for transaction_rollback: 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 AutoCAD MCP Pro. Nothing to install.
transaction_rollback 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 transaction_rollback 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 transaction_rollback. 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.
transaction_rollback is provided by the AutoCAD MCP Pro MCP server (u-c4n/autocad-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AutoCAD MCP Pro, 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.
108 AutoCAD MCP Pro tools catalogued and risk-classified — across an index of 43,000+ MCP servers.