Get information about an existing Devin session and optionally fetch associated Slack messages
AI agents call get_devin_session to retrieve information from MCP-Devin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about existing Devin sessions and their associated Slack messages without creating, modifying, deleting, or executing any operations. It is a pure read operation with no side effects, fitting the 'Read' category. The low severity reflects minimal blast radius - retrieving session information poses no risk of data loss, financial harm, or unintended operations.
From the tool's definition Tool description states 'Get information about an existing Devin session and optionally fetch associated Slack messages' - uses the verb 'Get' and 'fetch', which are read-only operations with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_devin_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 get_devin_session:
{
"version": "1",
"default": "deny",
"tools": {
"get_devin_session": {}
}
}get_devin_session is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get information about an existing Devin session and optionally fetch associated Slack messages. It is categorised as a Read tool in the MCP-Devin MCP Server, which means it retrieves data without modifying state.
Register the MCP-Devin MCP server in PolicyLayer and add a rule for get_devin_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.
get_devin_session is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_devin_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 get_devin_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.
get_devin_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.