delete_component
A destructive tool on the Enterprise-Multi-Agent-Engine MCP server.
This record as markdown: /tools/enterprise-multi-agent-engine/delete-component.md
What delete_component does on Enterprise-Multi-Agent-Engine
AI agents call delete_component to permanently remove resources in Enterprise-Multi-Agent-Engine, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_component is rated Critical
The 'delete_component' tool performs an irreversible operation that removes monitoring infrastructure. Even without a detailed description, the name unambiguously indicates a destructive action. In a monitoring context, deleting a component could disable monitoring of critical systems, affecting visibility and alerting capabilities.
From the tool's definition Tool name is 'delete_component' with no description provided. The verb 'delete' strongly indicates irreversible removal of data (a component in the Pingera monitoring system).
Attacks that exploit this kind of access
The rule that runs delete_component safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Enterprise-Multi-Agent-Engine, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_component, this is the rule to start with:
delete_component 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 Enterprise-Multi-Agent-Engine, apply this rule, and every delete_component call is checked against it from then on.
Questions about delete_component
delete_component is a destructive tool on the Enterprise-Multi-Agent-Engine MCP server. It is categorised as a Destructive tool in the Enterprise-Multi-Agent-Engine MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Enterprise-Multi-Agent-Engine MCP server in PolicyLayer and add a rule for delete_component: 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 Enterprise-Multi-Agent-Engine. Nothing to install.
delete_component 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 delete_component 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 delete_component. 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.
delete_component is provided by the Enterprise-Multi-Agent-Engine MCP server (Mojtaba-Dehghani/Enterprise-Multi-Agent-Engine). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Enterprise-Multi-Agent-Engine, and thousands of servers like it.
Across the catalogue