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 MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs data retrieval and querying only. It accesses project and room metadata from a local database without creating, modifying, deleting, or executing external operations. The blast radius of misuse is minimal—an agent could retrieve sensitive project information but cannot cause irreversible changes or financial impact.
From the tool's definition Tool description explicitly states 'Query stored Revit project and room data' with operations limited to 'get all projects', 'get project by ID/name', 'get rooms by project', 'get all rooms', or 'get database statistics'.
Documented attack patterns abuse exactly the kind of access query_stored_data 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 query_stored_data:
{
"version": "1",
"default": "deny",
"tools": {
"query_stored_data": {}
}
}query_stored_data 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.
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 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 MCP. 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 (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.