conv_change_status

Change a conversation\

SERVERMunin SOURCEhttps://mcp.getmunin.com/mcp

Medium RISK CLASS

Category Write

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-change-status.md

WHAT IT DOES

What conv_change_status does on Munin

AI agents use conv_change_status 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.

RISK

Why conv_change_status is rated Medium

The tool changes the status of a conversation, which is a reversible modification to existing data. This fits the Write category. Severity is medium as misuse could affect customer communication workflows. Confidence is moderate due to the truncated/incomplete description.

From the tool's definition 'conv_change_status' and 'Change a conversation' indicate modifying the status of a conversation record

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs conv_change_status 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_change_status, this is the rule to start with:

conv_change_status Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "conv_change_status": {
      "limits": [
        {
          "counter": "conv_change_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Munin, apply this rule, and every conv_change_status call is checked against it from then on.

FAQ

Questions about conv_change_status

What does the conv_change_status tool do? +

Change a conversation\. 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.

How do I enforce a policy on conv_change_status? +

Register the Munin MCP server in PolicyLayer and add a rule for conv_change_status: 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_change_status? +

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

Can I rate-limit conv_change_status? +

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

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

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

KEEP EXPLORING

More on Munin, and thousands of servers like it.

This server

All 242 Munin tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →