Disconnect this project from DevFlow. Removes .devflow.json and stops the heartbeat.
AI agents call devflow_disconnect to permanently remove resources in DevFlow MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly removes the .devflow.json configuration file that links the project to DevFlow, and stops the heartbeat monitoring. Deleting the configuration file cannot be undone without reconfiguring from scratch, making this a Destructive action.
From the tool's definition 'Removes .devflow.json and stops the heartbeat' — permanently deletes the project configuration file and terminates the heartbeat process
Attacks that exploit this kind of access
Disconnect this project from DevFlow. Removes .devflow.json and stops the heartbeat. It is categorised as a Destructive tool in the DevFlow MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the DevFlow MCP Server MCP server in PolicyLayer and add a rule for devflow_disconnect: 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 DevFlow MCP Server. Nothing to install.
devflow_disconnect is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the devflow_disconnect 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 devflow_disconnect. 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.
devflow_disconnect is provided by the DevFlow MCP Server MCP server (klausfreiberufler/devflow-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 →