AI agents use create_lights_definition 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.
The tool creates (rather than merely reads or executes) a new definition object within a building energy model. This is reversible (definitions can be deleted), so it falls under Write rather than Destructive. The blast radius is medium because an incorrectly created lights definition could affect simulation accuracy and downstream decisions, but effects are limited to model configuration and can be corrected.
From the tool's definition Tool name 'create_lights_definition' indicates creation of a new lights definition object in OpenStudio building energy simulation model. Server description confirms this enables 'creation...of models.' No description provided, lowering confidence slightly.
Documented attack patterns abuse exactly the kind of access create_lights_definition 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 create_lights_definition:
{
"version": "1",
"default": "deny",
"tools": {
"create_lights_definition": {
"limits": [
{
"counter": "create_lights_definition_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_lights_definition 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.
create_lights_definition. 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 create_lights_definition: 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.
create_lights_definition 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 create_lights_definition 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 create_lights_definition. 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.
create_lights_definition 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.