Create and place rooms in Revit at specified locations. Rooms are placed within enclosed wall boundaries and can be named and numbered. The location point should be inside an enclosed area bounded by walls. All coordinates are in millimeters (mm).
AI agents use create_room to create or update resources in Revit MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revit MCP environment.
This tool creates new elements (rooms) in a Revit project, which is reversible modification. While rooms can be deleted later, the creation action itself is a Write operation that changes project data. Severity is medium because room creation in architectural models can affect design workflows and downstream dependencies, but the action is not irreversible (rooms can be deleted) nor destructive in nature.
From the tool's definition Tool description explicitly states it will 'Create and place rooms in Revit' at specified locations, modifying the model by adding new room elements.
Documented attack patterns abuse exactly the kind of access create_room gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Revit MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_room:
{
"version": "1",
"default": "deny",
"tools": {
"create_room": {
"limits": [
{
"counter": "create_room_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_room 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.
Create and place rooms in Revit at specified locations. Rooms are placed within enclosed wall boundaries and can be named and numbered. The location point should be inside an enclosed area bounded by walls. All coordinates are in millimeters (mm). It is categorised as a Write tool in the Revit MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Revit MCP server in PolicyLayer and add a rule for create_room: 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 Revit MCP. Nothing to install.
create_room 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 create_room 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 create_room. 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.
create_room is provided by the Revit MCP server (mcp-servers-for-revit/revit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Revit MCP, 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.
25 Revit MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.