Remove a run's pin so it becomes eligible for automatic cleanup again.
AI agents use unpin_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.
This tool modifies the state of a run (removes its pin), making it eligible for cleanup. It's a reversible metadata change (you could re-pin it), so it falls under Write rather than Destructive. However, the downstream consequence is that the run may be automatically deleted, which raises the severity to medium.
From the tool's definition Remove a run's pin so it becomes eligible for automatic cleanup again
Documented attack patterns abuse exactly the kind of access unpin_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 unpin_run:
{
"version": "1",
"default": "deny",
"tools": {
"unpin_run": {
"limits": [
{
"counter": "unpin_run_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} unpin_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.
Remove a run's pin so it becomes eligible for automatic cleanup again. 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 unpin_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.
unpin_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 unpin_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 unpin_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.
unpin_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.