AI agents use import_floorspacejs to create or update resources in Openstudio — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Openstudio environment.
Import operations create or modify model data (building geometry, spaces, surfaces) within the simulation environment. This is reversible through model editing or deletion, so it does not qualify as Destructive. It could have significant downstream effects on simulation validity and results, warranting high severity.
From the tool's definition Tool name 'import_floorspacejs' indicates importing external floor space data/geometry into an OpenStudio building model. The server description states it enables 'creation...of models' and 'modification of models'.
Documented attack patterns abuse exactly the kind of access import_floorspacejs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Openstudio, and nothing reaches the server without passing your rules. This is the rule we recommend for import_floorspacejs:
{
"version": "1",
"default": "deny",
"tools": {
"import_floorspacejs": {
"limits": [
{
"counter": "import_floorspacejs_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}import_floorspacejs 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.
import_floorspacejs. It is categorised as a Write tool in the Openstudio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Openstudio MCP server in PolicyLayer and add a rule for import_floorspacejs: 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 Openstudio. Nothing to install.
import_floorspacejs 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 import_floorspacejs 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 import_floorspacejs. 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.
import_floorspacejs is provided by the Openstudio MCP server (natlabrockies/openstudio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Openstudio, 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.
146 Openstudio tools catalogued and risk-classified — across an index of 43,000+ MCP servers.