list_versions

Lists every published ISM release (historical, current, and any future tags as soon as they appear upstream). Returns tag, version id, commit SHA, and release date parsed from the tag.

Server ISM MCP Server rusticeagle/ism-mcp
Category Read
Risk class Low
Parameters 00 required

What list_versions does on ISM MCP Server

AI agents call list_versions to retrieve information from ISM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why list_versions needs a policy

This is a pure read operation that queries and returns information about ISM release versions. It has no side effects, does not execute code, does not modify data, and does not delete anything. The metadata returned (tags, version IDs, commit SHAs, release dates) is informational only.

From the tool's definition Tool 'lists every published ISM release' with 'returns tag, version id, commit SHA, and release date' — retrieves metadata about ISM versions without modifying any data.

Risk signalsBulk/mass operation — affects multiple targets

Questions about list_versions

What does the list_versions tool do? +

Lists every published ISM release (historical, current, and any future tags as soon as they appear upstream). Returns tag, version id, commit SHA, and release date parsed from the tag. It is categorised as a Read tool in the ISM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on list_versions? +

Register the ISM MCP Server MCP server in PolicyLayer and add a rule for list_versions: 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 ISM MCP Server. Nothing to install.

What risk level is list_versions? +

list_versions is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_versions? +

Yes. Add a rate_limit block to the list_versions 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.

How do I block list_versions completely? +

Set action: deny in the PolicyLayer policy for list_versions. 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.

What MCP server provides list_versions? +

list_versions is provided by the ISM MCP Server MCP server (rusticeagle/ism-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

list_versions is one line of ISM MCP Server's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.