Retrieves historical analysis data for a specific customer, including all previous analyses, trends, and active alerts. THIS REQUIRES DATABASE ACCESS - Claude cannot do this alone!
AI agents call get_customer_history to retrieve information from Sentiment Evolution Tracker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves existing data from a customer history database without modifying, deleting, or executing external operations. It is clearly a Read operation.
From the tool's definition Tool 'retrieves historical analysis data' (exact quote from description). No modification or deletion of data. Outputs sentiment trends, analyses, and alerts for a customer.
Attacks that exploit this kind of access
Retrieves historical analysis data for a specific customer, including all previous analyses, trends, and active alerts. THIS REQUIRES DATABASE ACCESS - Claude cannot do this alone!. It is categorised as a Read tool in the Sentiment Evolution Tracker MCP Server, which means it retrieves data without modifying state.
Register the Sentiment Evolution Tracker MCP server in PolicyLayer and add a rule for get_customer_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 Sentiment Evolution Tracker. Nothing to install.
get_customer_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_customer_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_customer_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_customer_history is provided by the Sentiment Evolution Tracker MCP server (rubenreyesss/mcp-nlp-analytics). 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 →