Query stored Revit project and room data from the local database. Supports various query types: get all projects, get project by ID/name, get rooms by project, get all rooms, or get database statistics.
AI agents call query_stored_data to retrieve information from Revit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries existing data from a local database without creating, modifying, deleting, or executing any operations. It is a pure read operation that poses minimal security risk—an AI agent misusing this tool would at worst retrieve architectural or project data, which has low blast radius compared to tools that modify or delete models.
From the tool's definition Tool description explicitly states 'Query stored Revit project and room data' and lists query operations: 'get all projects, get project by ID/name, get rooms by project, get all rooms, or get database statistics.' These are all read-only retrieval operations…
Attacks that exploit this kind of access
Query stored Revit project and room data from the local database. Supports various query types: get all projects, get project by ID/name, get rooms by project, get all rooms, or get database statistics. It is categorised as a Read tool in the Revit MCP Server, which means it retrieves data without modifying state.
Register the Revit MCP server in PolicyLayer and add a rule for query_stored_data: 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. Nothing to install.
query_stored_data 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 query_stored_data 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 query_stored_data. 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.
query_stored_data is provided by the Revit MCP server (mohamed-elnahla/revit-mcp-github-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →