zernio_list_whatsapp_contacts

List all WhatsApp contacts for a connected WhatsApp Business account.

SERVERZernio SOURCEeyalm321/zernio-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-zernio-mcp/zernio-list-whatsapp-contacts.md

WHAT IT DOES

What zernio_list_whatsapp_contacts does on Zernio

AI agents call zernio_list_whatsapp_contacts to retrieve information from Zernio without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why zernio_list_whatsapp_contacts is rated Low

This tool queries and retrieves contact data from a WhatsApp Business account without creating, modifying, deleting, or executing any operations. It is a straightforward read operation. Severity is low because while contact lists may contain personal data, the tool itself performs only passive retrieval with no destructive or financial implications.

From the tool's definition Tool name contains 'list' and description explicitly states 'List all WhatsApp contacts' — a retrieval operation with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs zernio_list_whatsapp_contacts safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Zernio, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For zernio_list_whatsapp_contacts, this is the rule to start with:

zernio_list_whatsapp_contacts Allowed

zernio_list_whatsapp_contacts is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "zernio_list_whatsapp_contacts": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Zernio, apply this rule, and every zernio_list_whatsapp_contacts call is checked against it from then on.

FAQ

Questions about zernio_list_whatsapp_contacts

What does the zernio_list_whatsapp_contacts tool do? +

List all WhatsApp contacts for a connected WhatsApp Business account. It is categorised as a Read tool in the Zernio MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zernio_list_whatsapp_contacts? +

Register the Zernio MCP server in PolicyLayer and add a rule for zernio_list_whatsapp_contacts: 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 Zernio. Nothing to install.

What risk level is zernio_list_whatsapp_contacts? +

zernio_list_whatsapp_contacts is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zernio_list_whatsapp_contacts? +

Yes. Add a rate_limit block to the zernio_list_whatsapp_contacts 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.

How do I block zernio_list_whatsapp_contacts completely? +

Set action: deny in the PolicyLayer policy for zernio_list_whatsapp_contacts. 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.

What MCP server provides zernio_list_whatsapp_contacts? +

zernio_list_whatsapp_contacts is provided by the Zernio MCP server (eyalm321/zernio-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Zernio, and thousands of servers like it.

This server

All 274 Zernio tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →