locus_determine_from_scores
Compute a LOCUS Level of Care from dimension ratings you already have. Deterministic — no LLM, instant: composite + Determination Grid + the inviolable override floors (e.g. Risk-of-Harm=4 → minimum Level 5), applied in code. Provide EITHER the seven flat D* ratings (1-5 each; Dimension IV splits...
This record as markdown: /tools/com-meta-council-decision-intelligence/locus-determine-from-scores.md
What locus_determine_from_scores does on Meta Council
AI agents call locus_determine_from_scores 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
D4A_Stress | integer | — | Recovery Environment — Stress (1-5). |
D4B_Support | integer | — | Recovery Environment — Support (1-5). |
agent_scores | object | — | Per-reviewer scores keyed by reviewer name, aggregated by median. Shape: {"<reviewer>": {"D1_RiskOfHarm": 4, ...}}. Mutually exclusive with the flat D* fields — |
D1_RiskOfHarm | integer | — | Risk of Harm (1-5). |
D6_Engagement | integer | — | Engagement & Recovery Status (1-5). |
D3_CoMorbidity | integer | — | Medical/Addictive/Psychiatric Co-Morbidity (1-5). Capital M in CoMorbidity. |
D2_FunctionalStatus | integer | — | Functional Status (1-5). |
D5_TreatmentHistory | integer | — | Treatment & Recovery History (1-5). |
Parameters from the server's own tool schema.
Why locus_determine_from_scores is rated Low
Even though locus_determine_from_scores only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs locus_determine_from_scores 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 locus_determine_from_scores, this is the rule to start with:
locus_determine_from_scores 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 locus_determine_from_scores call is checked against it from then on.
Questions about locus_determine_from_scores
Compute a LOCUS Level of Care from dimension ratings you already have. Deterministic — no LLM, instant: composite + Determination Grid + the inviolable override floors (e.g. Risk-of-Harm=4 → minimum Level 5), applied in code. Provide EITHER the seven flat D* ratings (1-5 each; Dimension IV splits into IV-A Stress / IV-B Support) OR a per-reviewer agent_scores map. Sending both is refused (422) rather than scored: agent_scores would win and your flat ratings would be discarded, override floors included. Requires authentication. It is categorised as a Read tool in the Meta Council MCP Server, which means it retrieves data without modifying state.
locus_determine_from_scores accepts 8 parameters: D4A_Stress, D4B_Support, agent_scores, D1_RiskOfHarm, D6_Engagement, D3_CoMorbidity, D2_FunctionalStatus, D5_TreatmentHistory. The full parameter table on this page comes from the server's own tool schema.
Register the Meta Council MCP server in PolicyLayer and add a rule for locus_determine_from_scores: 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.
locus_determine_from_scores 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 locus_determine_from_scores 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 locus_determine_from_scores. 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.
locus_determine_from_scores 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