Verify if a specific version exists for a Maven dependency
AI agents call check_version_exists to retrieve information from Maven Version Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves metadata from Maven Central to verify version existence. It has no side effects—it only queries and returns a boolean or status result. It does not create, modify, delete, or execute any operations. This is a straightforward read operation with minimal security risk.
From the tool's definition Tool performs verification/query operation to check if a version exists; described as checking whether a specific version exists for a dependency with no modification or deletion of data.
Attacks that exploit this kind of access
Verify if a specific version exists for a Maven dependency. It is categorised as a Read tool in the Maven Version Server MCP Server, which means it retrieves data without modifying state.
Register the Maven Version Server MCP server in PolicyLayer and add a rule for check_version_exists: 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 Maven Version Server. Nothing to install.
check_version_exists is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the check_version_exists 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 check_version_exists. 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.
check_version_exists is provided by the Maven Version Server MCP server (kristijan-rotim/maven-version-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →