Create tags for all rooms in the current active view. Tags will be placed at the center point of each room, displaying the room name and number.
AI agents use tag_all_rooms 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 annotation elements (tags) in the Revit model, which is a reversible write operation. While it modifies the project by adding visual elements, these additions can be undone/deleted without permanent data loss. It does not execute arbitrary code, delete elements irreversibly, or affect financial systems.
From the tool's definition Tool creates tags for all rooms in the current view, placing them at center points with room name and number displayed. The verb 'create' and action of 'placing' tags indicates data creation and modification of the model.
Documented attack patterns abuse exactly the kind of access tag_all_rooms 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 tag_all_rooms:
{
"version": "1",
"default": "deny",
"tools": {
"tag_all_rooms": {
"limits": [
{
"counter": "tag_all_rooms_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} tag_all_rooms 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 tags for all rooms in the current active view. Tags will be placed at the center point of each room, displaying the room name and number. 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 tag_all_rooms: 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.
tag_all_rooms 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 tag_all_rooms 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 tag_all_rooms. 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.
tag_all_rooms 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.