This record as markdown: /tools/io-github-dave-london-github/maven-verify.md
What maven-verify does on Github
AI agents invoke maven-verify to trigger actions in Github. 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's 'verify' phase runs the full build lifecycle up to and including integration tests, which involves executing code. The description is truncated/uninformative ('Runs' with nothing following), so confidence is reduced. Based on the tool name, this is an Execute category action — it compiles and runs tests but does not inherently delete data or move money.
From the tool's definition Tool name 'maven-verify' implies running the Maven 'verify' lifecycle phase, which executes code compilation, testing, and verification steps
Attacks that exploit this kind of access
The rule that runs maven-verify safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Github, 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:
maven-verify 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 Github, apply this rule, and every maven-verify call is checked against it from then on.
Questions about maven-verify
Runs. It is categorised as a Execute tool in the Github MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Github MCP server in PolicyLayer and add a rule for maven-verify: 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 Github. Nothing to install.
maven-verify 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 maven-verify 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 maven-verify. 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.
maven-verify is provided by the Github MCP server (@paretools/github). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Github, and thousands of servers like it.
Across the catalogue