AI agents use send_contact to create or update resources in Automagik Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Automagik Tools environment.
The 'send_contact' action most likely creates, modifies, or transmits contact data to an external system or recipient. This is reversible (contacts can be deleted or corrected) and does not irreversibly destroy data or execute arbitrary code. Classified as Write rather than Execute because it appears to perform a specific, bounded operation (sending contact info) rather than arbitrary command execution.
From the tool's definition Tool name 'send_contact' indicates it sends or transmits contact information. The description is empty, limiting direct evidence, but the name and sibling tools (add_contact, add_source) on a communication/API platform suggest data modification operations.
Documented attack patterns abuse exactly the kind of access send_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 send_contact:
{
"version": "1",
"default": "deny",
"tools": {
"send_contact": {
"limits": [
{
"counter": "send_contact_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_contact stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
send_contact. It is categorised as a Write tool in the Automagik Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Automagik Tools MCP server in PolicyLayer and add a rule for send_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.
send_contact is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the send_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 send_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.
send_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.