Chapter aggregate + per-member metric breakdown. chapter = SALES | PRODUCT | GROWTH | ENGINEER.
AI agents call kpi_chapter to retrieve information from Wealify Kpi without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves aggregated metrics and breakdowns for a specific chapter (SALES, PRODUCT, GROWTH, or ENGINEER). It performs data retrieval only—querying existing KPI information with no side effects, modifications, or destructive operations. The read-only server constraint and the query nature of the tool confirm the Read category.
From the tool's definition Server is explicitly described as 'Read-only MCP server' and tool provides 'Chapter aggregate + per-member metric breakdown' which retrieves and queries KPI data without modification capabilities.
Attacks that exploit this kind of access
Chapter aggregate + per-member metric breakdown. chapter = SALES | PRODUCT | GROWTH | ENGINEER. It is categorised as a Read tool in the Wealify Kpi MCP Server, which means it retrieves data without modifying state.
Register the Wealify Kpi MCP server in PolicyLayer and add a rule for kpi_chapter: 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 Wealify Kpi. Nothing to install.
kpi_chapter 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 kpi_chapter 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 kpi_chapter. 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.
kpi_chapter is provided by the Wealify Kpi MCP server (ngkienmkqn/wealify-kpi-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 →