Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color.
AI agents use color_elements 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 modifies the visual appearance of elements in the current Revit view by applying colors. It is a reversible modification (colors can be changed or reset), making it a Write operation. The blast radius is medium since it affects the visual state of potentially many elements in a view, but does not delete or irreversibly alter model data.
From the tool's definition 'Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color.'
Documented attack patterns abuse exactly the kind of access color_elements 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 color_elements:
{
"version": "1",
"default": "deny",
"tools": {
"color_elements": {
"limits": [
{
"counter": "color_elements_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} color_elements 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.
Color elements in the current view based on a category and parameter value. Each unique parameter value gets assigned a distinct color. 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 color_elements: 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.
color_elements 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 color_elements 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 color_elements. 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.
color_elements 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.