Create a new GitHub App integration
AI agents use create_github_app to create or update resources in Coolify MCP Tools — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify MCP Tools environment.
This tool creates a new GitHub App integration, which is a reversible write operation that establishes a new external authentication/authorization credential/integration. While it modifies infrastructure state and could pose risks if misconfigured (excessive permissions, credential exposure), it is not inherently destructive, financial, or code-executing.
From the tool's definition Tool name 'create_github_app' and description 'Create a new GitHub App integration' indicate creation of a new integration artifact.
Attacks that exploit this kind of access
Create a new GitHub App integration. It is categorised as a Write tool in the Coolify MCP Tools MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP Tools MCP server in PolicyLayer and add a rule for create_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.
create_github_app 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 create_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 create_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.
create_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 →