conv_list_conversations
List conversations for your org, newest activity first. Filter by status (open / snoozed / closed / spam), assignee, topic, handover state (
This record as markdown: /tools/com-getmunin-munin/conv-list-conversations.md
What conv_list_conversations does on Munin
AI agents call conv_list_conversations to retrieve information from Munin without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why conv_list_conversations is rated Low
Retrieves and queries conversation data without modifying or deleting information.
From the tool's definition List conversations for your org, newest activity first. Filter by status, assignee, topic.
Attacks that exploit this kind of access
The rule that runs conv_list_conversations 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_list_conversations, this is the rule to start with:
conv_list_conversations is read-only, so it stays allowed. 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_list_conversations call is checked against it from then on.
Questions about conv_list_conversations
List conversations for your org, newest activity first. Filter by status (open / snoozed / closed / spam), assignee, topic, handover state (. It is categorised as a Read tool in the Munin MCP Server, which means it retrieves data without modifying state.
Register the Munin MCP server in PolicyLayer and add a rule for conv_list_conversations: 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_list_conversations is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the conv_list_conversations 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_list_conversations. 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_list_conversations 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.
This server
Across the catalogue