View the activity log. Optionally filter by item name.
AI agents call view_history to retrieve information from Inventory 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 reads and displays an activity log with optional filtering. It performs no write, delete, execution, or financial operations. The lowest blast radius applies — an AI agent querying logs cannot cause data loss or unintended modifications.
From the tool's definition Tool named 'view_history' with description 'View the activity log. Optionally filter by item name.' — this queries and retrieves historical data without modification or side effects.
Attacks that exploit this kind of access
View the activity log. Optionally filter by item name. It is categorised as a Read tool in the Inventory Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Inventory Tracker MCP Server MCP server in PolicyLayer and add a rule for view_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 Inventory Tracker MCP Server. Nothing to install.
view_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 view_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 view_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.
view_history is provided by the Inventory Tracker MCP Server MCP server (pborlagdan/inventory-mcp-server). 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 →