Send a reply in a conversation. The reply is sent through the original channel (e.g., Instagram comment, X reply, Facebook comment, etc.). Replies require conversation reply routing metadata (credential + operation). Provide "routing" once and it will be stored on the conversation for future repl...
Risk signalsAccepts raw HTML/template content (content)
Part of the SendIt server.
Free to start. No card required.
AI agents use reply_to_conversation to create or modify resources in SendIt. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call reply_to_conversation repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SendIt.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"reply_to_conversation": {
"limits": [
{
"counter": "reply_to_conversation_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full SendIt policy for all 148 tools.
These attack patterns abuse exactly the kind of access reply_to_conversation gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Send a reply in a conversation. The reply is sent through the original channel (e.g., Instagram comment, X reply, Facebook comment, etc.). Replies require conversation reply routing metadata (credential + operation). Provide "routing" once and it will be stored on the conversation for future replies. Use the Inbox Reply agent to get AI-drafted replies with brand voice.. It is categorised as a Write tool in the SendIt MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the SendIt MCP server in PolicyLayer and add a rule for reply_to_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 SendIt. Nothing to install.
reply_to_conversation 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_to_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.
Set action: deny in the PolicyLayer policy for reply_to_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.
reply_to_conversation is provided by the SendIt MCP server (https://sendit.infiniteappsai.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 148 SendIt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.