Validate server connection and configuration
AI agents call validate_server 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 performs validation and diagnostics—retrieving and checking server status and configuration. It has no side effects, does not modify data, execute code, delete resources, or commit financial transactions. It is purely informational, similar to health checks or status queries (cf. sibling tool 'coolify_health').
From the tool's definition Tool name 'validate_server' and description 'Validate server connection and configuration' indicate a query/check operation that tests connectivity and reads configuration state without modifying or executing changes.
Attacks that exploit this kind of access
Validate server connection and configuration. 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 validate_server: 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.
validate_server 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 validate_server 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 validate_server. 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.
validate_server is provided by the Coolify MCP Server MCP server (pavelsukhachev/mcp-server-coolify). 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 →