compare_versions

Computes the diff between two ISM releases: controls added, removed, and modified (title, statement, or applicability changes). Useful for change-management and gap analysis.

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

What compare_versions does on ISM MCP Server

AI agents call compare_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 compare_versions needs a policy

The tool performs read-only operations: it retrieves and compares historical versions of ISM controls to compute differences. There is no data creation, modification, deletion, code execution, or financial impact. The output is analytical information derived from existing documentation.

From the tool's definition Tool description states it 'computes the diff between two ISM releases' and retrieves information about controls that were 'added, removed, and modified'. This is a comparison and analysis operation with no side effects on the underlying ISM data.

Questions about compare_versions

What does the compare_versions tool do? +

Computes the diff between two ISM releases: controls added, removed, and modified (title, statement, or applicability changes). Useful for change-management and gap analysis. 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 compare_versions? +

Register the ISM MCP Server MCP server in PolicyLayer and add a rule for compare_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 compare_versions? +

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

Can I rate-limit compare_versions? +

Yes. Add a rate_limit block to the compare_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 compare_versions completely? +

Set action: deny in the PolicyLayer policy for compare_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 compare_versions? +

compare_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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.