delete_github_app

Delete a GitHub App (only if not used by any applications).

SERVERCoolify SOURCEcoolify-mcp-server

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/coolify/delete-github-app.md

WHAT IT DOES

What delete_github_app does on Coolify

AI agents call delete_github_app to permanently remove resources in Coolify, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why delete_github_app is rated Critical

This tool performs an irreversible deletion operation on a GitHub App resource. Although the description includes a precondition ('only if not used by any applications'), the core action is destructive—once deleted, the GitHub App cannot be recovered. This falls squarely into the Destructive category, which takes precedence over Write (which is reversible).

From the tool's definition Tool name contains 'delete'; description states 'Delete a GitHub App', which is an irreversible removal of a GitHub App configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs delete_github_app safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Coolify, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_github_app, this is the rule to start with:

delete_github_app Hidden

delete_github_app is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_github_app"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Coolify, apply this rule, and every delete_github_app call is checked against it from then on.

FAQ

Questions about delete_github_app

What does the delete_github_app tool do? +

Delete a GitHub App (only if not used by any applications). It is categorised as a Destructive tool in the Coolify MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_github_app? +

Register the Coolify 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. Nothing to install.

What risk level is delete_github_app? +

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.

Can I rate-limit delete_github_app? +

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.

How do I block delete_github_app completely? +

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.

What MCP server provides delete_github_app? +

delete_github_app is provided by the Coolify MCP server (coolify-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Coolify, and thousands of servers like it.

This server

All 111 Coolify tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →