unregister_instance_runtime
Remove the registered runtime endpoint for one of your private instances.
This record as markdown: /tools/io-github-proagentstore-platform/unregister-instance-runtime.md
What unregister_instance_runtime does on ProAgentStore
AI agents call unregister_instance_runtime to permanently remove resources in ProAgentStore, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why unregister_instance_runtime is rated Critical
This tool permanently deletes/deregisters a runtime configuration, making it an irreversible action. While it does not delete data files directly, deregistering a runtime endpoint effectively disables a private instance and cannot be undone without re-registration. The high severity reflects that an agent misusing this could take down production runtime infrastructure.
From the tool's definition Remove the registered runtime endpoint for one of your private instances — this action is irreversible and prevents the instance from functioning.
Attacks that exploit this kind of access
The rule that runs unregister_instance_runtime safely
PolicyLayer is an MCP gateway: it sits between your AI agents and ProAgentStore, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For unregister_instance_runtime, this is the rule to start with:
unregister_instance_runtime is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect ProAgentStore, apply this rule, and every unregister_instance_runtime call is checked against it from then on.
Questions about unregister_instance_runtime
Remove the registered runtime endpoint for one of your private instances. It is categorised as a Destructive tool in the ProAgentStore MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the ProAgentStore MCP server in PolicyLayer and add a rule for unregister_instance_runtime: 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 ProAgentStore. Nothing to install.
unregister_instance_runtime is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the unregister_instance_runtime 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 unregister_instance_runtime. 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.
unregister_instance_runtime is provided by the ProAgentStore MCP server (https://mcp.proagentstore.online/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on ProAgentStore, and thousands of servers like it.
Across the catalogue