Check if an application name is available in a project
AI agents call coolify.check_name_conflicts to retrieve information from Coolify MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of application names within a project to determine availability. It has no side effects, does not modify data, does not execute code or operations, and does not affect deployments or resources. It is purely informational, fitting the Read category with low severity since misuse would only return false information about name availability without causing harm to infrastructure or data.
From the tool's definition Tool name and description indicate it performs a check/query operation: 'Check if an application name is available in a project'. This is a read-only operation that retrieves availability status without modifying, deleting, or executing any side effects.
Attacks that exploit this kind of access
Check if an application name is available in a project. It is categorised as a Read tool in the Coolify MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for coolify.check_name_conflicts: 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 Server. Nothing to install.
coolify.check_name_conflicts is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the coolify.check_name_conflicts 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 coolify.check_name_conflicts. 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.
coolify.check_name_conflicts is provided by the Coolify MCP Server MCP server (thedurancode/coolify-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 →