Reply to a received message by msg_id. Auto-completes tasks when replying to task messages.
AI agents use reply to create or update resources in CC2CC — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your CC2CC environment.
The tool creates new reply messages and modifies task completion state. While reversible (messages can be sent, tasks marked incomplete), it has broader impact because it affects inter-agent communication state and task tracking. This is Write rather than Execute because it doesn't run arbitrary code or trigger unpredictable external operations—it performs a specific, bounded state modification.
From the tool's definition Tool modifies state by replying to messages and auto-completing tasks ('Reply to a received message by msg_id. Auto-completes tasks when replying to task messages'). These are write operations that create new message records and change task status.
Documented attack patterns abuse exactly the kind of access reply gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CC2CC, and nothing reaches the server without passing your rules. This is the rule we recommend for reply:
{
"version": "1",
"default": "deny",
"tools": {
"reply": {
"limits": [
{
"counter": "reply_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}reply 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.
Free to start. No card required.
Reply to a received message by msg_id. Auto-completes tasks when replying to task messages. It is categorised as a Write tool in the CC2CC MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the CC2CC MCP server in PolicyLayer and add a rule for 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 CC2CC. Nothing to install.
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 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 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.
reply is provided by the CC2CC MCP server (non4me/cc2cc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CC2CC, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 CC2CC tools catalogued and risk-classified — across an index of 43,000+ MCP servers.