Get elements currently selected in Revit. You can limit the number of returned elements.
AI agents call get_selected_elements to retrieve information from Revit MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the current selection state from Revit without modifying, deleting, executing commands, or triggering external operations. It is a simple data query with no side effects, fitting the Read category. Severity is low because reading element metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_selected_elements' and description 'Get elements currently selected in Revit' indicate a retrieval operation with 'You can limit the number of returned elements' confirming read-only query semantics.
Documented attack patterns abuse exactly the kind of access get_selected_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 get_selected_elements:
{
"version": "1",
"default": "deny",
"tools": {
"get_selected_elements": {}
}
} get_selected_elements is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get elements currently selected in Revit. You can limit the number of returned elements. It is categorised as a Read tool in the Revit MCP MCP Server, which means it retrieves data without modifying state.
Register the Revit MCP server in PolicyLayer and add a rule for get_selected_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.
get_selected_elements is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_selected_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 get_selected_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.
get_selected_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.