Skip to main content
Glama

Get remediation policy

get_remediation_policy
Read-only

The organisation's AI auto-remediation policy (the read twin of GET /api/v1/org/ai-remediation/policy), the only surface carrying autonomy_level, tier_overrides, cluster_allow_list and cluster_exclude_list: get_ai_settings reports only whether the policy is enabled, and pause_ai_autonomy is the org-wide soft switch, a different thing. configured is the field to read first: false means the organisation has NO policy row, so every other field is the built-in default document (disabled, autonomy_level 'propose', no overrides, no allow list) rather than a setting anyone chose, and must never be reported as a configured policy. autonomy_level is one of read_only, propose or auto. tier_overrides maps a tool name to auto, approval or never, where auto means that tool executes with NO approval card; anything else, including an unknown value, keeps the human gate, and auto_tier_tools is the subset that really runs unattended; lowered_to_approval names tools stored as auto that are confirm-only, so a person approves every call anyway, and they must never be reported as running automatically. cluster_scope names which clusters the remediation dispatcher acts on: 'all_clusters' when no allow list is set, so every cluster in the organisation is in scope; 'listed_clusters' when the list names clusters, which also puts a trigger with no cluster out of scope; 'no_clusters' when the list is present but empty, which admits nothing. cluster_exclude_list names clusters that are out of scope whatever the allow list says, so an excluded cluster gets no remediation run in every one of those cases. Also returns the approvers, the Slack webhook id, the per-incident action cap, the cooldown and updated_at. Read-only and readable by any member, exactly like the REST read; writing the policy stays a portal or admin API lane.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_remediation_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true; the description goes far beyond that by disclosing that `configured: false` means no policy row exists and every other field is a built-in default that must never be reported as a configured policy. It additionally spells out the semantics of `autonomy_level`, `tier_overrides` (including that 'auto' bypasses approval while unknown values keep the human gate), `auto_tier_tools`, `lowered_to_approval`, and all three `cluster_scope` states — exactly the interpretive context an agent needs to avoid misreporting.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Identity and sibling differentiation are front-loaded, and every subsequent clause covers a distinct field or a distinct failure mode. It is dense and long, but the length is load-bearing; only small internal repetition (e.g. restating that excluded clusters get no remediation in every case) could be trimmed.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description carries the full burden of explaining the return shape, and it does so thoroughly: configuration state, autonomy levels, tier override semantics, cluster scope vocabulary, exclude list, plus approvers, Slack webhook id, action cap, cooldown and updated_at. Nothing an agent needs to interpret the response correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so there is no parameter surface to document; the baseline for a zero-param tool is 4. The description spends its space on return-field semantics instead, which is the right allocation here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific resource ('the organisation's AI auto-remediation policy') and frames it precisely via the 'read twin of GET /api/v1/org/ai-remediation/policy', then explicitly separates it from `get_ai_settings` (enabled flag only) and `pause_ai_autonomy` (org-wide soft switch). An agent can distinguish this from all three sibling surfaces without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to reach for this tool ('the only surface carrying autonomy_level, tier_overrides, cluster_allow_list and cluster_exclude_list') and where the boundary lies: writing the policy stays in the portal or admin API lane. It also instructs read order for the response ('`configured` is the field to read first'), which is usage guidance grounded in this tool's actual shape.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.