Update a project
AI agents use update_project 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.
The tool modifies project data (update) rather than reading it (Read), executing arbitrary code (Execute), permanently deleting it (Destructive), or moving money (Financial). The blast radius is medium because project updates could affect infrastructure configuration, deployed applications, and team settings, but changes are typically reversible.
From the tool's definition Tool name 'update_project' and description 'Update a project' indicate modification of project configuration or metadata. The verb 'update' in both name and description clearly indicates a write operation that modifies existing data reversibly.
Attacks that exploit this kind of access
Update a project. 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 update_project: 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.
update_project 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_project 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_project. 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_project 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 →