conv_set_topic
Tag a conversation with one of the org\
This record as markdown: /tools/com-getmunin-munin/conv-set-topic.md
What conv_set_topic does on Munin
AI agents use conv_set_topic to create or update resources in Munin, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Munin environment.
Why conv_set_topic is rated Medium
This tool modifies conversation attributes (tags/topics) but does not delete or execute external code. The operation is reversible—tags can be changed or removed. It affects data organization within the CRM/conversation module but has limited blast radius unless mass-tagging could disrupt workflows. Classified as Write rather than Read (which would be 'get_topic') or Destructive (tags are not irreversibly deleted).
From the tool's definition Tool name 'conv_set_topic' and description 'Tag a conversation with one of the org' indicates modification of conversation metadata. 'Set' is a write operation that creates or modifies data reversibly.
Attacks that exploit this kind of access
The rule that runs conv_set_topic 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_set_topic, this is the rule to start with:
conv_set_topic stays usable, but capped: an agent stuck in a loop can't make hundreds of changes 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_set_topic call is checked against it from then on.
Questions about conv_set_topic
Tag a conversation with one of the org\. It is categorised as a Write tool in the Munin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Munin MCP server in PolicyLayer and add a rule for conv_set_topic: 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_set_topic is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the conv_set_topic 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_set_topic. 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_set_topic 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