Update a database
AI agents use update_database to create or update resources in Coolify MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Coolify MCP Server environment.
This tool modifies database configuration or state reversibly (Write category). Severity is high due to blast radius: database updates in a production PaaS environment could cause service disruption, data corruption, or configuration errors if misused by an AI agent. However, it is not Destructive (no irreversible deletion) or Financial.
From the tool's definition Tool name 'update_database' and description 'Update a database' indicate modification of data. The server context shows this is for managing Coolify PaaS instances with direct operational control.
Attacks that exploit this kind of access
Update a database. It is categorised as a Write tool in the Coolify MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Coolify MCP Server MCP server in PolicyLayer and add a rule for update_database: 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.
update_database 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 update_database 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 update_database. 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.
update_database 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 →