This record as markdown: /tools/vamerli-elementify-mcp/delete-amelia-service.md
What delete_amelia_service does on Elementify MCP
AI agents call delete_amelia_service to permanently remove resources in Elementify MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why delete_amelia_service is rated Critical
This tool permanently removes a service record from the Amelia booking system with no stated undo capability. Deletion is irreversible and constitutes a destructive action. The high severity reflects that an AI agent with unrestricted use could remove critical booking services, disrupting business operations. Confidence is high because the intent is unambiguous from both name and description.
From the tool's definition Tool name 'delete_amelia_service' explicitly indicates deletion. The description states 'Delete an Amelia service,' which is an irreversible removal of data/configuration.
Attacks that exploit this kind of access
The rule that runs delete_amelia_service safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Elementify MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_amelia_service, this is the rule to start with:
delete_amelia_service 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 Elementify MCP, apply this rule, and every delete_amelia_service call is checked against it from then on.
Questions about delete_amelia_service
Delete an Amelia service. It is categorised as a Destructive tool in the Elementify MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Elementify MCP server in PolicyLayer and add a rule for delete_amelia_service: 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 Elementify MCP. Nothing to install.
delete_amelia_service 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_amelia_service 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_amelia_service. 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_amelia_service is provided by the Elementify MCP server (vamerli/elementify-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Elementify, and thousands of servers like it.
Across the catalogue