zernio_set_messenger_menu

Set or update the Facebook Messenger persistent menu -- the quick-action buttons shown in your Messenger chat.

SERVERZernio SOURCEeyalm321/zernio-mcp
Medium RISK CLASS
Category Write
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/eyalm321-zernio-mcp/zernio-set-messenger-menu.md

What zernio_set_messenger_menu does on Zernio

AI agents use zernio_set_messenger_menu to create or update resources in Zernio, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zernio environment.

Why zernio_set_messenger_menu is rated Medium

The tool modifies messenger menu settings, which are reversible changes to platform configuration. This is a Write operation (update) rather than Read (no data retrieval), Execute (no code execution or external triggers), Destructive (changes are reversible), or Financial (no money movement).

From the tool's definition Tool description states "Set or update the Facebook Messenger persistent menu" — this creates or modifies UI configuration that affects customer interactions, with no permanent data deletion.

Questions about zernio_set_messenger_menu

What does the zernio_set_messenger_menu tool do? +

Set or update the Facebook Messenger persistent menu -- the quick-action buttons shown in your Messenger chat. It is categorised as a Write tool in the Zernio MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on zernio_set_messenger_menu? +

Register the Zernio MCP server in PolicyLayer and add a rule for zernio_set_messenger_menu: 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_set_messenger_menu? +

zernio_set_messenger_menu is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit zernio_set_messenger_menu? +

Yes. Add a rate_limit block to the zernio_set_messenger_menu 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_set_messenger_menu completely? +

Set action: deny in the PolicyLayer policy for zernio_set_messenger_menu. 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_set_messenger_menu? +

zernio_set_messenger_menu 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.

More on Zernio, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Zernio's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.