delete_bot_env_var

Delete a bot environment variable

SERVERinstantKOM MCP Server SOURCEinstantkom/mcp-server
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/instantkom-mcp-server/delete-bot-env-var.md

What delete_bot_env_var does on instantKOM MCP Server

AI agents call delete_bot_env_var to permanently remove resources in instantKOM MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete_bot_env_var is rated Critical

Deleting an environment variable is an irreversible operation that cannot be undone. Environment variables often contain sensitive configuration, API keys, or runtime parameters critical to bot operation. Loss of these variables could break bot functionality or require manual recovery. This meets the Destructive category (cannot undo) rather than Write (reversible modification).

From the tool's definition Tool name explicitly states 'delete' a bot environment variable; description confirms irreversible removal of configuration data.

Questions about delete_bot_env_var

What does the delete_bot_env_var tool do? +

Delete a bot environment variable. It is categorised as a Destructive tool in the instantKOM MCP Server 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 delete_bot_env_var? +

Register the instantKOM MCP Server MCP server in PolicyLayer and add a rule for delete_bot_env_var: 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 instantKOM MCP Server. Nothing to install.

What risk level is delete_bot_env_var? +

delete_bot_env_var 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 delete_bot_env_var? +

Yes. Add a rate_limit block to the delete_bot_env_var 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 delete_bot_env_var completely? +

Set action: deny in the PolicyLayer policy for delete_bot_env_var. 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 delete_bot_env_var? +

delete_bot_env_var is provided by the instantKOM MCP Server MCP server (instantkom/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on instantKOM MCP Server, 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 instantKOM MCP Server'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.