Store or update Revit project metadata in the local database. This captures project information with a timestamp for later retrieval.
AI agents use store_project_data 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 writes project metadata to a local database, which is a reversible write operation. It does not delete data, execute code, or involve financial transactions. Severity is medium because misuse could corrupt or overwrite important project metadata, but it is limited to metadata and is reversible.
From the tool's definition 'Store or update Revit project metadata in the local database' — creates or modifies data reversibly with a timestamp for later retrieval
Documented attack patterns abuse exactly the kind of access store_project_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 store_project_data:
{
"version": "1",
"default": "deny",
"tools": {
"store_project_data": {
"limits": [
{
"counter": "store_project_data_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} store_project_data 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.
Store or update Revit project metadata in the local database. This captures project information with a timestamp for later retrieval. 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 store_project_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.
store_project_data 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 store_project_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 store_project_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.
store_project_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.