CMake build system operations: configure, build, test, list-presets, install, clean.
AI agents invoke cmake to trigger actions in Http. 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.
CMake build operations execute external processes and have significant side effects on the filesystem (creating build artifacts, installing files, cleaning directories). While not inherently destructive (can be reversed), execution of build systems poses high risk if an AI agent misuses the tool with malicious or incorrect build configurations.
From the tool's definition Tool performs CMake build system operations including configure, build, test, install, and clean - these are executable operations that run external commands and processes whose effects depend on the build configuration and project arguments provided.
Documented attack patterns abuse exactly the kind of access cmake gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Http, and nothing reaches the server without passing your rules. This is the rule we recommend for cmake:
{
"version": "1",
"default": "deny",
"tools": {
"cmake": {
"limits": [
{
"counter": "cmake_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}cmake 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.
CMake build system operations: configure, build, test, list-presets, install, clean. It is categorised as a Execute tool in the Http MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Http MCP server in PolicyLayer and add a rule for cmake: 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 Http. Nothing to install.
cmake 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 cmake 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 cmake. 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.
cmake is provided by the Http MCP server (@paretools/http). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Http, 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 Http tools catalogued and risk-classified — across an index of 43,000+ MCP servers.