AI agents call ism_history 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 designed to retrieve historical data or audit trails related to ISM controls, policies, or coverage tracking. No evidence suggests mutation, deletion, execution, or financial operations. The 'history' function is a standard Read operation that interrogates existing data without side effects, consistent with the server's purpose as a 'query layer' for information discovery.
From the tool's definition Tool name 'ism_history' with context from sibling tools (ism_get, ism_list_by_classification, ism_coverage_read) strongly suggests retrieval of historical records or version history.
Attacks that exploit this kind of access
ism_history. 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_history: 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_history 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_history 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_history. 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_history 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 →