Retrieves version history for Product or Active Context.
AI agents call get_item_history to retrieve information from SDOF Knowledge Base without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a retrieval operation ('Retrieves') on version history, which is a read-only query with no side effects. There is no indication that it modifies, deletes, executes, or commits financial actions. The low severity reflects that accessing historical metadata poses minimal risk even if misused by an AI agent.
From the tool's definition Tool name 'get_item_history' and description 'Retrieves version history for Product or Active Context' indicate a query operation that reads historical data without modifying it.
Attacks that exploit this kind of access
Retrieves version history for Product or Active Context. It is categorised as a Read tool in the SDOF Knowledge Base MCP Server, which means it retrieves data without modifying state.
Register the SDOF Knowledge Base MCP server in PolicyLayer and add a rule for get_item_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 SDOF Knowledge Base. Nothing to install.
get_item_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 get_item_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 get_item_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.
get_item_history is provided by the SDOF Knowledge Base MCP server (tgf-between-your-legs/sdof-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 →