get_high_risk_customers

Returns list of all customers currently at high risk of churn. THIS REQUIRES DATABASE ACCESS - Claude cannot do this alone!

Server Sentiment Evolution Tracker rubenreyesss/mcp-nlp-analytics
Category Read
Risk class Low
Parameters 00 required

What get_high_risk_customers does on Sentiment Evolution Tracker

AI agents call get_high_risk_customers 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.

Why get_high_risk_customers needs a policy

This is a Read operation as it retrieves customer risk data from a database. Severity is medium rather than low because the sensitive nature of the data returned (high-risk customer identities and churn predictions) could enable harmful downstream actions if misused by an AI agent (e.g., targeting vulnerable customers for predatory practices, or exposing PII).

From the tool's definition Tool returns a list of customers 'currently at high risk of churn' - it retrieves and queries data without modifying, deleting, or executing external operations. The description indicates data retrieval ('Returns list'), not creation or deletion.

Questions about get_high_risk_customers

What does the get_high_risk_customers tool do? +

Returns list of all customers currently at high risk of churn. 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.

How do I enforce a policy on get_high_risk_customers? +

Register the Sentiment Evolution Tracker MCP server in PolicyLayer and add a rule for get_high_risk_customers: 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.

What risk level is get_high_risk_customers? +

get_high_risk_customers is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_high_risk_customers? +

Yes. Add a rate_limit block to the get_high_risk_customers 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.

How do I block get_high_risk_customers completely? +

Set action: deny in the PolicyLayer policy for get_high_risk_customers. 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.

What MCP server provides get_high_risk_customers? +

get_high_risk_customers 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.