AI agents use store_project_data to create or update resources in Revit — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revit environment.
This tool writes project metadata to a local database. It is reversible (data can be updated or overwritten) and has limited blast radius — it only stores metadata, not modifying actual Revit model elements. This fits the Write category as it creates/modifies data in a database but does not execute code, delete data, or involve financial transactions.
From the tool's definition 'Store or update Revit project metadata in the local database' and 'captures project information with a timestamp for later retrieval'
Attacks that exploit this kind of access
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 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. 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 (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 →