Protect a run from automatic age-based cleanup (keep it indefinitely).
AI agents use pin_run 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 modifies an attribute of an existing run (its protection/cleanup status) but does not delete data, execute external code, or cause financial impact. It is reversible (a run can be unpinned). This is a Write operation with low severity because the modification is administrative in nature and affects only metadata; misuse would prevent cleanup but cause no direct harm to simulation data or results.
From the tool's definition Tool description states 'Protect a run from automatic age-based cleanup', which modifies the retention/lifecycle properties of an existing run object. This is a metadata update operation that changes how the system treats the run going forward.
Documented attack patterns abuse exactly the kind of access pin_run 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 pin_run:
{
"version": "1",
"default": "deny",
"tools": {
"pin_run": {
"limits": [
{
"counter": "pin_run_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}pin_run 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.
Protect a run from automatic age-based cleanup (keep it indefinitely). 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 pin_run: 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.
pin_run 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 pin_run 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 pin_run. 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.
pin_run 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.