Elimina la configuración de un tool. Si es multi-instance, también la remueve de enabledTools automáticamente.
AI agents call remove_tool_config to permanently remove resources in BotUyo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes a tool's configuration and automatically removes it from the enabled tools list. Deletion of configuration data is a destructive, non-reversible operation. Misuse by an AI agent could disable critical agent capabilities without easy recovery, warranting high severity.
From the tool's definition "Elimina la configuración de un tool" (deletes the tool configuration) and "también la remueve de enabledTools automáticamente" (also removes it from enabledTools automatically)
Attacks that exploit this kind of access
Elimina la configuración de un tool. Si es multi-instance, también la remueve de enabledTools automáticamente. It is categorised as a Destructive tool in the BotUyo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the BotUyo MCP Server MCP server in PolicyLayer and add a rule for remove_tool_config: 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 BotUyo MCP Server. Nothing to install.
remove_tool_config 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 remove_tool_config 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 remove_tool_config. 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.
remove_tool_config is provided by the BotUyo MCP Server MCP server (marcoar1/botuyo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →