Get environment variables for an application
AI agents call get_application_envs 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 retrieves application environment variables without modifying them or triggering external operations. It is a straightforward read-only query operation. The blast radius is minimal—unauthorized access to environment variables could expose sensitive data like API keys or credentials, but the tool itself does not enable execution, modification, deletion, or financial actions.
From the tool's definition Tool name 'get_application_envs' and description 'Get environment variables for an application' indicate a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
Get environment variables for an application. 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 get_application_envs: 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.
get_application_envs 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 get_application_envs 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 get_application_envs. 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.
get_application_envs is provided by the Coolify MCP Server MCP server (kof70/coolify-mcp-server). 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 →