AI agents invoke maven-build to trigger actions in Go. 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.
Maven build execution is a code execution operation that can trigger arbitrary plugin code and affect the filesystem. While not destructive by itself, it has significant side effects (compilation, artifact generation, test execution) and could be misused to inject malicious builds. High severity due to potential for supply chain attacks or unintended system modifications.
From the tool's definition Tool name 'maven-build' combined with server description indicating 'build' output suggests execution of a build process. Maven build commands compile code, run tests, and can execute arbitrary plugins/scripts.
Attacks that exploit this kind of access
Runs. It is categorised as a Execute tool in the Go MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Go MCP server in PolicyLayer and add a rule for maven-build: 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 Go. Nothing to install.
maven-build 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-build 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-build. 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-build is provided by the Go MCP server (Dave-London/Pare). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.