semver_compare
Semantic Version Compare / Bump — Compare two semver 2.0.0 versions by precedence, or bump a version's major/minor/patch.
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/semver-compare.md
What semver_compare does on Gateway
AI agents call semver_compare to retrieve information from Gateway without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
mode | string | — | compare | bump (default compare) |
version | string | — | Version to bump (mode=bump) |
bump_type | string | — | major | minor | patch (mode=bump) |
version_a | string | — | First version (mode=compare) |
version_b | string | — | Second version (mode=compare) |
Parameters from the server's own tool schema.
Why semver_compare is rated Low
This tool performs pure computation on version strings — comparing precedence or calculating a bumped version. It has no side effects, does not write or delete data, and does not execute external operations. It is a read/calculation-only tool.
From the tool's definition Compare two semver 2.0.0 versions by precedence, or bump a version's major/minor/patch
Attacks that exploit this kind of access
The rule that runs semver_compare safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gateway, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For semver_compare, this is the rule to start with:
semver_compare is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gateway, apply this rule, and every semver_compare call is checked against it from then on.
Questions about semver_compare
Semantic Version Compare / Bump — Compare two semver 2.0.0 versions by precedence, or bump a version's major/minor/patch. It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
semver_compare accepts 5 parameters: mode, version, bump_type, version_a, version_b. The full parameter table on this page comes from the server's own tool schema.
Register the Gateway MCP server in PolicyLayer and add a rule for semver_compare: 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 Gateway. Nothing to install.
semver_compare 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 semver_compare 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 semver_compare. 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.
semver_compare is provided by the Gateway MCP server (https://wingmanprotocol.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gateway, and thousands of servers like it.
This server
Across the catalogue