remove_contact
Remove contact from local database. Args: phone_number. Returns: confirmation.
This record as markdown: /tools/namastexlabs-automagik-tools/remove-contact.md
What remove_contact does on Automagik Tools
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.
Why remove_contact is rated Critical
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.
Attacks that exploit this kind of access
The rule that runs remove_contact safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Automagik Tools, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For remove_contact, this is the rule to start with:
remove_contact 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 Automagik Tools, apply this rule, and every remove_contact call is checked against it from then on.
Questions about remove_contact
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.
More on Automagik Tools, and thousands of servers like it.
Across the catalogue