Add a reply or internal note to a conversation (also called a ticket) in SparrowDesk
AI agents use add_conversation_reply 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.
This tool creates or appends data (a reply or note) to a conversation without deleting or overwriting existing data, and does not execute arbitrary code or move financial resources. It is reversible (replies can typically be edited or removed in ticketing systems).
From the tool's definition Tool description explicitly states 'Add a reply or internal note to a conversation' — this creates new content (reply/note) within an existing ticket/conversation, modifying the state reversibly.
Attacks that exploit this kind of access
Add a reply or internal note to a conversation (also called a ticket) in SparrowDesk. 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.
Register the SparrowDesk MCP server in PolicyLayer and add a rule for add_conversation_reply: 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.
add_conversation_reply 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 add_conversation_reply 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 add_conversation_reply. 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.
add_conversation_reply 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →