update_conversation · SparrowDesk MCP: Risk & Policy

WHAT IT DOES

What update_conversation does on SparrowDesk

AI agents use update_conversation to create or update resources in SparrowDesk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SparrowDesk environment.

WHY IT NEEDS A POLICY

Why update_conversation needs a policy

This tool creates or modifies data in a reversible manner. Updates to conversation metadata (subject, status, priority, assignment) can all be undone by subsequent updates. There is no deletion, destruction, or financial impact. The medium severity reflects that misuse could disrupt ticket management workflows or improperly escalate/reassign support issues, but changes remain recoverable.

From the tool's definition Tool description explicitly states 'Update an existing conversation' with modifiable fields including subject, status, priority, assignment, and custom fields.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_conversation Rate-limited

update_conversation 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": {
    "update_conversation": {
      "limits": [
        {
          "counter": "update_conversation_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches SparrowDesk, so you can run agents against it safely.

FAQ

Questions about update_conversation

What does the update_conversation tool do? +

Update an existing conversation (subject, status, priority, assignment, custom fields). It is categorised as a Write tool in the SparrowDesk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_conversation? +

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

What risk level is update_conversation? +

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

Can I rate-limit update_conversation? +

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

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

update_conversation is provided by the SparrowDesk MCP server (sparrowdesk/sparrowdesk-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.