Skip to main content
Glama

Pause AI autonomy

pause_ai_autonomy
Destructive

Pause autonomous AI actions for the organisation (the twin of ankra ai autonomy pause): the auto-remediation policy is disabled and every enabled agent is paused in one transaction, recorded server-side so any surface can resume it. Chat and diagnosis keep working; nothing unapproved changes until resume. Refused when already paused. Requires ai.manage; a credential held to one project may pause. The answer's autonomy.paused_through records the credential this call paused through; null means not recorded (a database the recording has not reached), never organisation-wide. This is the soft pause, not the kill switch that cancels live sessions.

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": "pause_ai_autonomy"
  }
}

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy autonomy is being paused; shown with the pause record.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations only declare destructiveHint=true, readOnlyHint=false and idempotentHint=false; the description goes much further by explaining that chat and diagnosis keep working, nothing unapproved changes until resume, the pause is transactional and server-recorded, and invocation is refused when already paused. It also discloses the autonomy.paused_through return semantics and the null-means-unrecorded edge case. The only small gap is that 'destructive' is not reconciled with the reversible nature of a pause.

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?

The core action and its effects are front-loaded in the first sentence, and each following sentence adds a distinct constraint or return-value caveat. It is dense with parenthetical asides and the CLI twin reference, which could be trimmed, but nothing is redundant filler.

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 compensates by explaining what the response records via autonomy.paused_through and what null means. Combined with permissions, refusal condition and reversibility, an agent has everything needed to call and interpret this correctly.

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

Parameters3/5

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

There is a single optional parameter with 100% schema description coverage, so the baseline is 3. The description does not add anything about the reason field beyond what the schema already says; its detail about autonomy.paused_through concerns output, not input.

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?

States a specific verb and resource with scope: 'Pause autonomous AI actions for the organisation', and specifies the mechanism (auto-remediation policy disabled plus every enabled agent paused in one transaction). It also distinguishes itself from the kill-switch concept and from the resume path, so an agent can identify it without opening the 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?

Gives explicit preconditions and exclusions: refused when already paused, requires ai.manage, project-scoped credentials may pause, and it is the soft pause rather than the kill switch that cancels live sessions. An agent knows both when to call it and when the behaviour is not what it wants.

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.