AI agents call ism_versions to retrieve information from Ism without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool appears to fetch or list version records of ISM controls—a read-only informational query. No evidence suggests data modification, deletion, code execution, or financial impact. Low severity reflects minimal blast radius if an agent misuses version retrieval.
From the tool's definition Tool name 'ism_versions' and server context suggest retrieval of version information from ISM controls documentation.
Attacks that exploit this kind of access
ism_versions. It is categorised as a Read tool in the Ism MCP Server, which means it retrieves data without modifying state.
Register the Ism MCP server in PolicyLayer and add a rule for ism_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. Nothing to install.
ism_versions 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 ism_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.
Set action: deny in the PolicyLayer policy for ism_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.
ism_versions is provided by the Ism MCP server (samueldudley/ism-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →