Send a message to an existing Devin session and optionally to the associated Slack thread
AI agents use send_message_to_session to create or update resources in MCP-Devin — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP-Devin environment.
This tool sends messages to a Devin AI session and Slack thread. It creates/posts new messages (reversible write operation). While it could trigger actions in Devin, the primary function described is messaging/communication, not executing code directly. Misuse could send unauthorized instructions to Devin sessions or spam Slack threads.
From the tool's definition Send a message to an existing Devin session and optionally to the associated Slack thread
Documented attack patterns abuse exactly the kind of access send_message_to_session gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP-Devin, and nothing reaches the server without passing your rules. This is the rule we recommend for send_message_to_session:
{
"version": "1",
"default": "deny",
"tools": {
"send_message_to_session": {
"limits": [
{
"counter": "send_message_to_session_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} send_message_to_session 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.
Send a message to an existing Devin session and optionally to the associated Slack thread. It is categorised as a Write tool in the MCP-Devin MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP-Devin MCP server in PolicyLayer and add a rule for send_message_to_session: 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 MCP-Devin. Nothing to install.
send_message_to_session 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 send_message_to_session 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 send_message_to_session. 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.
send_message_to_session is provided by the MCP-Devin MCP server (kazuph/mcp-devin). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP-Devin, 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.
5 MCP-Devin tools catalogued and risk-classified — across an index of 43,000+ MCP servers.