Checks a Nix flake for errors and returns structured check results, warnings, and errors.
AI agents invoke flake-check to trigger actions in Make. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Running 'nix flake check' executes Nix code evaluation and potentially builds derivations to verify correctness. This is an active execution of code/build processes, not merely a passive read. While it doesn't modify or delete data, it triggers external operations (Nix evaluation engine, builds) whose effects depend on the flake contents.
From the tool's definition 'Checks a Nix flake for errors' — running a flake check involves executing Nix evaluation and build processes
Documented attack patterns abuse exactly the kind of access flake-check 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-check:
{
"version": "1",
"default": "deny",
"tools": {
"flake-check": {
"limits": [
{
"counter": "flake-check_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}flake-check stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Checks a Nix flake for errors and returns structured check results, warnings, and errors. It is categorised as a Execute tool in the Make MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Make MCP server in PolicyLayer and add a rule for flake-check: 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-check is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the flake-check 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-check. 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-check 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.