Delete a GitHub App integration
AI agents call delete_github_app to permanently remove resources in Coolify MCP Tools — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deleting a GitHub App integration is an irreversible destructive action that removes authentication and connection configuration. This cannot be undone without reconfiguration, affecting CI/CD pipelines, deployment automation, and application lifecycle management tied to that integration. While not directly deleting user data, it destroys infrastructure configuration with significant operational impact.
From the tool's definition Tool name is 'delete_github_app' with description 'Delete a GitHub App integration'. The verb 'delete' indicates irreversible removal of a configured integration.
Attacks that exploit this kind of access
Delete a GitHub App integration. It is categorised as a Destructive tool in the Coolify MCP Tools MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for delete_github_app: 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 Coolify MCP Tools. Nothing to install.
delete_github_app 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 delete_github_app 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 delete_github_app. 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.
delete_github_app is provided by the Coolify MCP Tools MCP server (jplansink/coolify-mcp-tools). 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 →