cmake

CMake build system operations: configure, build, test, list-presets, install, clean.

SERVERGit SOURCEDave-London/Pare

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-dave-london-git/cmake.md

WHAT IT DOES

What cmake does on Git

AI agents invoke cmake to trigger actions in Git. 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.

RISK

Why cmake is rated High

CMake operations execute external processes that compile source code, run tests, and install artifacts. While not directly destructive (build artifacts can be cleaned), the build and install operations execute arbitrary code from build scripts and can modify the system state. This meets Execute criteria as effects depend on the CMakeLists.txt arguments and system configuration.

From the tool's definition Tool performs "configure, build, test, install, clean" operations—these are external build system commands that execute code compilation and installation with real side effects depending on arguments.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs cmake safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Git, 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 Rate-limited

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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cmake": {
      "limits": [
        {
          "counter": "cmake_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Git, apply this rule, and every cmake call is checked against it from then on.

FAQ

Questions about cmake

What does the cmake tool do? +

CMake build system operations: configure, build, test, list-presets, install, clean. It is categorised as a Execute tool in the Git MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cmake? +

Register the Git 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 Git. Nothing to install.

What risk level is cmake? +

cmake is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cmake? +

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.

How do I block cmake completely? +

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.

What MCP server provides cmake? +

cmake is provided by the Git MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Git, and thousands of servers like it.

This server

All 202 Git tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →