get_deal_health
Health scores for the caller's OPEN deals: each scored 0-100 on how likely it is to be slipping (healthy >= 70 / watch / at_risk), worst first, with plain-language reasons — days since last logged contact, whether it is past its own expected close date, and how its age compares to the caller's av...
This record as markdown: /tools/com-meta-council-decision-intelligence/get-deal-health.md
What get_deal_health does on Meta Council
AI agents call get_deal_health to retrieve information from Meta Council without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_deal_health is rated Low
This tool performs purely informational queries on deal data that the authenticated caller already has access to. It computes and returns analytics (health scores 0-100, contact history, cycle comparisons) with no side effects, no external actions, and no data modification. It is explicitly stated as 'read-only,' making it a classic Read category tool.
From the tool's definition 'Read-only and deterministic over the caller's own deals + activities; nothing is executed or sent.' The tool retrieves health scores and metrics for open deals without modifying, executing, or sending anything.
Attacks that exploit this kind of access
The rule that runs get_deal_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Meta Council, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_deal_health, this is the rule to start with:
get_deal_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Meta Council, apply this rule, and every get_deal_health call is checked against it from then on.
Questions about get_deal_health
Health scores for the caller's OPEN deals: each scored 0-100 on how likely it is to be slipping (healthy >= 70 / watch / at_risk), worst first, with plain-language reasons — days since last logged contact, whether it is past its own expected close date, and how its age compares to the caller's average won-deal cycle. Includes per-band counts, an average score, and the reference cycle. Read-only and deterministic over the caller's own deals + activities; nothing is executed or sent. Pair with get_sales_recommendations to act on what is slipping. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
Register the Meta Council MCP server in PolicyLayer and add a rule for get_deal_health: 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 Meta Council. Nothing to install.
get_deal_health 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_deal_health 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_deal_health. 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_deal_health is provided by the Meta Council MCP server (https://meta-council.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Meta Council, and thousands of servers like it.
This server
Across the catalogue