get_item_history
AI agents call get_item_history to retrieve information from Expense Tracker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'get_item_history' follows standard naming patterns for read-only retrieval functions ('get_'). The server explicitly lists querying purchase history as a capability, and this tool logically fits that function. While the description is empty (lowering confidence slightly), the name and server context are sufficient to classify this as a Read operation with no side effects.
From the tool's definition Tool name 'get_item_history' combined with server purpose of querying 'purchase history and spending patterns' indicates data retrieval. No description provided, but naming convention and context strongly suggest a query/fetch operation.
Attacks that exploit this kind of access
get_item_history. It is categorised as a Read tool in the Expense Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Expense Tracker MCP Server 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 Expense Tracker MCP Server. 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 Expense Tracker MCP Server MCP server (sharan0402/expense-tracker-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 →