semver_satisfies_range
Semantic Version Range Satisfaction — Check whether a semver 2.0.0 version satisfies a node-semver-style range (comparators, caret ^, tilde ~, and || alternatives).
This record as markdown: /tools/com-wingmanprotocol-agent-gateway/semver-satisfies-range.md
What semver_satisfies_range does on Gateway
AI agents call semver_satisfies_range 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 |
|---|---|---|---|
range | string | Yes | Range expression, e.g. '^1.2.3' or '>=1.2.7 <1.3.0' |
version | string | Yes | The version to test, e.g. '1.2.4' |
Parameters from the server's own tool schema.
Why semver_satisfies_range is rated Low
This tool reads and validates semantic version data against range specifications without side effects. It does not create, modify, delete, or execute any operations—only returns a boolean result indicating whether a version satisfies a given range constraint. This is a pure read/query operation with minimal blast radius if misused by an AI agent.
From the tool's definition Tool performs a check/validation operation ('satisfies a node-semver-style range') with no modification, deletion, or execution of code. It is purely a query against semantic version specifications.
Attacks that exploit this kind of access
The rule that runs semver_satisfies_range 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_satisfies_range, this is the rule to start with:
semver_satisfies_range 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_satisfies_range call is checked against it from then on.
Questions about semver_satisfies_range
Semantic Version Range Satisfaction — Check whether a semver 2.0.0 version satisfies a node-semver-style range (comparators, caret ^, tilde ~, and || alternatives). It is categorised as a Read tool in the Gateway MCP Server, which means it retrieves data without modifying state.
semver_satisfies_range accepts 2 parameters: range, version. Required: range, version. 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_satisfies_range: 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_satisfies_range 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_satisfies_range 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_satisfies_range. 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_satisfies_range 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