neuron_send_location
Send a location pin via WhatsApp with coordinates and optional name/address.
This record as markdown: /tools/io-github-conquext-neuron/neuron-send-location.md
What neuron_send_location does on Neuron
AI agents use neuron_send_location to create or update resources in Neuron, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Neuron environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | Yes | Recipient JID or phone number |
name | string | — | Location name (e.g. 'Eko Hotel') |
address | string | — | Street address |
latitude | number | Yes | Latitude in decimal degrees |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
longitude | number | Yes | Longitude in decimal degrees |
Parameters from the server's own tool schema.
Why neuron_send_location is rated Medium
This tool creates a new WhatsApp message containing location data and sends it to a recipient. It modifies the state of the messaging system by adding a new outbound message, which is reversible (messages can be deleted or unsent in WhatsApp).
From the tool's definition Tool name 'neuron_send_location' and description 'Send a location pin via WhatsApp with coordinates and optional name/address' indicate the tool creates and transmits a new message object (location data) to a WhatsApp contact.
Attacks that exploit this kind of access
The rule that runs neuron_send_location safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Neuron, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For neuron_send_location, this is the rule to start with:
neuron_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_send_location call is checked against it from then on.
Questions about neuron_send_location
Send a location pin via WhatsApp with coordinates and optional name/address. It is categorised as a Write tool in the Neuron MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
neuron_send_location accepts 6 parameters: to, name, address, latitude, channelId, longitude. Required: to, latitude, channelId, longitude. The full parameter table on this page comes from the server's own tool schema.
Register the Neuron MCP server in PolicyLayer and add a rule for neuron_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 Neuron. Nothing to install.
neuron_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 neuron_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 neuron_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.
neuron_send_location is provided by the Neuron MCP server (neuron-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Neuron, and thousands of servers like it.
This server
Across the catalogue