neuron_block_contact
Block a WhatsApp contact. Blocked contacts cannot message the bot or see its profile.
This record as markdown: /tools/io-github-conquext-neuron/neuron-block-contact.md
What neuron_block_contact does on Neuron
AI agents use neuron_block_contact 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 |
|---|---|---|---|
jid | string | Yes | Contact JID or phone number to block (e.g. '2348012345678' or '2348012345678@s.whatsapp.net') |
channelId | string | Yes | WhatsApp channel identifier (UUID) |
Parameters from the server's own tool schema.
Why neuron_block_contact is rated Medium
Blocking a contact is a reversible modification operation (contacts can typically be unblocked) that changes data permissions/relationships rather than creating new data or deleting it irreversibly. This fits the Write category (creates or modifies data reversibly).
From the tool's definition Tool performs 'Block a WhatsApp contact' which modifies the state of a contact relationship - blocked contacts cannot message or see profile. This is a state change operation that affects contact permissions.
Attacks that exploit this kind of access
The rule that runs neuron_block_contact 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_block_contact, this is the rule to start with:
neuron_block_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Neuron, apply this rule, and every neuron_block_contact call is checked against it from then on.
Questions about neuron_block_contact
Block a WhatsApp contact. Blocked contacts cannot message the bot or see its profile. 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_block_contact accepts 2 parameters: jid, channelId. Required: jid, channelId. 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_block_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 Neuron. Nothing to install.
neuron_block_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 neuron_block_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 neuron_block_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.
neuron_block_contact 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