New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

conv_request_callback

Place an outbound phone call to the contact in this conversation. Use this only when the user has asked to be called — e.g. \

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp
High RISK CLASS
Category Execute
Parameters 00 required
Recommended Rate-limitedsee the rule below
Registry record Grade D, identity unverified Pull the record →

This record as markdown: /tools/com-getmunin-munin/conv-request-callback.md

What conv_request_callback does on Munin

AI agents invoke conv_request_callback to trigger actions in Munin. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why conv_request_callback is rated High

This tool triggers an external real-world operation (an outbound phone call) to a contact. It is an Execute-category action because it initiates a live communication event whose effects depend on arguments (which contact/conversation to call). Misuse could result in unwanted calls being placed to customers, making severity high.

From the tool's definition Place an outbound phone call to the contact in this conversation

Questions about conv_request_callback

What does the conv_request_callback tool do? +

Place an outbound phone call to the contact in this conversation. Use this only when the user has asked to be called — e.g. \. It is categorised as a Execute tool in the Munin MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on conv_request_callback? +

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

What risk level is conv_request_callback? +

conv_request_callback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit conv_request_callback? +

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

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

conv_request_callback is provided by the Munin MCP server (https://mcp.getmunin.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Munin, 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 Munin'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.