Set NIST lifecycle cost analysis study period (1-40 years).
AI agents use set_lifecycle_cost_params 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.
This tool modifies building energy simulation configuration parameters (lifecycle cost study period), which is reversible and has no side effects beyond updating the model's lifecycle cost analysis settings. It does not execute code, delete data, or commit financial obligations—it merely configures an analysis parameter.
From the tool's definition Tool name 'set_lifecycle_cost_params' and description 'Set NIST lifecycle cost analysis study period' indicate modification of simulation parameters.
Documented attack patterns abuse exactly the kind of access set_lifecycle_cost_params 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 set_lifecycle_cost_params:
{
"version": "1",
"default": "deny",
"tools": {
"set_lifecycle_cost_params": {
"limits": [
{
"counter": "set_lifecycle_cost_params_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}set_lifecycle_cost_params 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.
Set NIST lifecycle cost analysis study period (1-40 years). 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 set_lifecycle_cost_params: 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.
set_lifecycle_cost_params 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 set_lifecycle_cost_params 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 set_lifecycle_cost_params. 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.
set_lifecycle_cost_params 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.