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. \
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
Attacks that exploit this kind of access
The rule that runs conv_request_callback safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Munin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For conv_request_callback, this is the rule to start with:
conv_request_callback stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every conv_request_callback call is checked against it from then on.
Questions about 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. \. 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.
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.
conv_request_callback is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Across the catalogue