Get elements visible in the currently active view in Revit. Returns per element: element_id, name, category, category_id. Also returns category_counts (always for ALL elements, even if truncated). If the response contains truncated=true, not all elements were returned. Check total_elements vs ret...
AI agents call get_current_view_elements to retrieve information from MCP server for Revit - Python without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval operation with no side effects. It fetches metadata about existing Revit model elements without creating, modifying, deleting, or executing any changes. The optional parameters (limit, include_levels, include_location) control what data is returned, not what actions are performed. This fits the Read category as a straightforward query/fetch operation.
From the tool's definition Tool retrieves information about elements visible in the currently active Revit view, returning element_id, name, category, category_id, and optionally level and location data.
Documented attack patterns abuse exactly the kind of access get_current_view_elements gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP server for Revit - Python, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_view_elements:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_view_elements": {}
}
}get_current_view_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 visible in the currently active view in Revit. Returns per element: element_id, name, category, category_id. Also returns category_counts (always for ALL elements, even if truncated). If the response contains truncated=true, not all elements were returned. Check total_elements vs returned_elements and increase limit if needed. Args: limit: Maximum number of elements to return (default 5000). include_levels: Include level name and level_id per element. Default false. include_location: Include location geometry (point or curve). Default false. It is categorised as a Read tool in the MCP server for Revit - Python MCP Server, which means it retrieves data without modifying state.
Register the MCP server for Revit - Python MCP server in PolicyLayer and add a rule for get_current_view_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 MCP server for Revit - Python. Nothing to install.
get_current_view_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_current_view_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_current_view_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_current_view_elements is provided by the MCP server for Revit - Python MCP server (mcp-servers-for-revit/mcp-server-for-revit-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP server for Revit - Python, 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.
20 MCP server for Revit - Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.