get_churn_signals

Get churn risk signals — declining engagement, negative sentiment trends, at-risk tenants. Returns actionable list.

Server Inkwell MCP Server mumega-com/inkwell
Category Read
Risk class Low
Parameters 00 required

What get_churn_signals does on Inkwell MCP Server

AI agents call get_churn_signals to retrieve information from Inkwell MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_churn_signals needs a policy

This tool queries and retrieves churn risk analytics data (declining engagement, sentiment trends, at-risk tenant information) to provide actionable insights. It performs a read-only analysis function with no side effects on data or systems. While the insights could inform business decisions, the tool itself only reads and returns information without creating, modifying, deleting, or executing any operations.

From the tool's definition Tool description states "Get churn risk signals" and "Returns actionable list" — retrieval and analysis of existing data with no modification, creation, deletion, or execution capability.

Questions about get_churn_signals

What does the get_churn_signals tool do? +

Get churn risk signals — declining engagement, negative sentiment trends, at-risk tenants. Returns actionable list. It is categorised as a Read tool in the Inkwell MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_churn_signals? +

Register the Inkwell MCP Server MCP server in PolicyLayer and add a rule for get_churn_signals: 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 Inkwell MCP Server. Nothing to install.

What risk level is get_churn_signals? +

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

Can I rate-limit get_churn_signals? +

Yes. Add a rate_limit block to the get_churn_signals 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_churn_signals completely? +

Set action: deny in the PolicyLayer policy for get_churn_signals. 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_churn_signals? +

get_churn_signals is provided by the Inkwell MCP Server MCP server (mumega-com/inkwell). 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.