maven-verify

What maven-verify does on Build

AI agents invoke maven-verify to trigger actions in Build. 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 maven-verify is rated High

Maven verify runs the full build lifecycle up to the verify phase, which compiles code, runs tests, and executes integration checks. This constitutes external command execution with potentially broad side effects depending on the project's build configuration. The description is minimal ('Runs' is truncated), lowering confidence slightly, but the tool name strongly implies command execution.

From the tool's definition Tool name 'maven-verify' implies running the Maven 'verify' lifecycle phase, which executes build, test, and verification steps. Server description mentions 'generic commands' executed as build tools.

The rule that runs maven-verify safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Build, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For maven-verify, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "maven-verify": {
      "limits": [
        {
          "counter": "maven-verify_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

Questions about maven-verify