New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

unregister_instance_runtime

Remove the registered runtime endpoint for one of your private instances.

SERVERProAgentStore SOURCEhttps://mcp.proagentstore.online/mcp
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade D, identity unverified Pull the record →

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.

Questions about unregister_instance_runtime

What does the unregister_instance_runtime tool do? +

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.

How do I enforce a policy on unregister_instance_runtime? +

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.

What risk level is unregister_instance_runtime? +

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.

Can I rate-limit unregister_instance_runtime? +

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.

How do I block unregister_instance_runtime completely? +

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.

What MCP server provides unregister_instance_runtime? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of ProAgentStore's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.