Remove contact from local database. Args: phone_number. Returns: confirmation.
AI agents call remove_contact to permanently remove resources in Automagik Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool deletes contact records from a database without ability to undo the operation. Even though the blast radius is limited to contact data rather than critical infrastructure or financial systems, the irreversible nature of data deletion classifies it as Destructive rather than Write. An AI agent could maliciously or accidentally delete important contact information.
From the tool's definition Tool name is 'remove_contact' and description states 'Remove contact from local database' with phone_number argument. The verb 'remove' combined with 'from local database' indicates irreversible deletion of data.
Documented attack patterns abuse exactly the kind of access remove_contact gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Automagik Tools, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_contact:
{
"version": "1",
"default": "deny",
"hide": [
"remove_contact"
]
}remove_contact disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Remove contact from local database. Args: phone_number. Returns: confirmation. It is categorised as a Destructive tool in the Automagik Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for remove_contact: 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 Automagik Tools. Nothing to install.
remove_contact 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_contact 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_contact. 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_contact is provided by the Automagik Tools MCP server (namastexlabs/automagik-tools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Automagik Tools, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
122 Automagik Tools tools catalogued and risk-classified — across an index of 43,000+ MCP servers.