Create a one-click service (e.g., penpot, n8n, wordpress)
AI agents use create_service 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 new service instances in the Coolify infrastructure, which is a reversible data/state modification operation (Write category). Severity is high because service provisioning can consume resources, affect system configuration, and create new attack surfaces, but it is not destructive (reversible), not directly executing arbitrary commands (Execute would require code injection via service args), and…
From the tool's definition Creates a one-click service instance (e.g., penpot, n8n, wordpress), which is a provisioning/deployment action that modifies infrastructure state by instantiating new services.
Attacks that exploit this kind of access
Create a one-click service (e.g., penpot, n8n, wordpress). 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_service: 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_service 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_service 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_service. 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_service 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 →