Updates flake lock file inputs and returns structured information about what was updated.
AI agents use flake-update to create or update resources in Make — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Make environment.
The tool updates a lock file, which is a reversible modification of data (dependencies can be reverted or updated again). It does not delete data irreversibly (not Destructive), does not execute arbitrary code (not Execute in the dangerous sense—it's a package manager operation), and does not involve financial transactions.
From the tool's definition Tool name 'flake-update' and description 'Updates flake lock file inputs' indicates it modifies the flake.lock file, a dependency manifest. This is a write operation that changes configuration state.
Documented attack patterns abuse exactly the kind of access flake-update gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Make, and nothing reaches the server without passing your rules. This is the rule we recommend for flake-update:
{
"version": "1",
"default": "deny",
"tools": {
"flake-update": {
"limits": [
{
"counter": "flake-update_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}flake-update stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Updates flake lock file inputs and returns structured information about what was updated. It is categorised as a Write tool in the Make MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Make MCP server in PolicyLayer and add a rule for flake-update: 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 Make. Nothing to install.
flake-update 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 flake-update 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 flake-update. 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.
flake-update is provided by the Make MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Make, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
202 Make tools catalogued and risk-classified — across an index of 43,000+ MCP servers.