Scoring-period state (OPEN | LOCKED) for a month. Use before nudging Leads or reading
AI agents call kpi_scoring_period 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 queries the current state of a scoring period for a given month. It has no capability to modify, delete, or execute operations. The description indicates it is used as a precondition check ('Use before nudging Leads or reading'), confirming its role as a data retrieval operation.
From the tool's definition Tool description states it retrieves 'Scoring-period state (OPEN | LOCKED) for a month' — a query operation with no side effects. Server is explicitly marked 'Read-only MCP server'. All sibling tools are read operations (list, get, query verbs).
Attacks that exploit this kind of access
Scoring-period state (OPEN | LOCKED) for a month. Use before nudging Leads or reading. 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_scoring_period: 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_scoring_period 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_scoring_period 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_scoring_period. 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_scoring_period 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 →