semver_compare
Compare two semantic versions (returns greater, less, or equal).
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/semver-compare.md
What semver_compare does on UnClick
AI agents call semver_compare to retrieve information from UnClick 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 |
|---|---|---|---|
version_a | string | Yes | First version. |
version_b | string | Yes | Second version. |
Parameters from the server's own tool schema.
Why semver_compare is rated Low
This tool performs a read-only comparison of semantic version strings and returns a relational outcome (greater, less, or equal). It does not create, modify, delete, or execute any operations—it simply computes and returns a comparison result based on input parameters. No data is changed, no external operations are triggered, and there is no destructive or financial impact. This is a low-risk utility function.
From the tool's definition Tool name 'semver_compare' and description 'Compare two semantic versions (returns greater, less, or equal)' indicate a pure comparison operation that retrieves and returns a result without side effects.
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 UnClick, 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 UnClick, apply this rule, and every semver_compare call is checked against it from then on.
Questions about semver_compare
Compare two semantic versions (returns greater, less, or equal). It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
semver_compare accepts 2 parameters: version_a, version_b. Required: version_a, version_b. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick 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 UnClick. 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 UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue