AI agents use send_location 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.
Based on the name alone, 'send_location' likely transmits or posts a geographic location to an external service or contact (e.g., via WhatsApp, given sibling tools like 'check_is_whatsapp'). Sending data to an external party is a Write/outbound operation. Severity is medium as it could expose location data. Confidence is low due to the empty description.
From the tool's definition Tool name 'send_location' — description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access send_location 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_location:
{
"version": "1",
"default": "deny",
"tools": {
"send_location": {
"limits": [
{
"counter": "send_location_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_location 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_location. 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_location: 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_location 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_location 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_location. 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_location 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.