cmake
CMake build system operations: configure, build, test, list-presets, install, clean.
This record as markdown: /tools/io-github-dave-london-pare-search/cmake.md
What cmake does on Search
AI agents invoke cmake to trigger actions in Search. 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.
Why cmake is rated High
CMake is a build system orchestrator that compiles and installs code based on configuration files. While not directly destructive in isolation, it can execute arbitrary build scripts, run test suites, and install binaries system-wide. The 'build' and 'install' operations trigger code execution with effects dependent on the CMakeLists.txt arguments.
From the tool's definition CMake operations include 'configure', 'build', 'test', 'install', and 'clean' — these are code execution and build system operations that trigger compilation, testing, and installation of software on the system.
Attacks that exploit this kind of access
The rule that runs cmake safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Search, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For cmake, this is the rule to start with:
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.
The button opens the PolicyLayer dashboard: create your workspace, connect Search, apply this rule, and every cmake call is checked against it from then on.
Questions about cmake
CMake build system operations: configure, build, test, list-presets, install, clean. It is categorised as a Execute tool in the Search MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Search 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 Search. 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 Search MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Search, and thousands of servers like it.
Across the catalogue