Skip to main content
Glama
cipp-mcp

cipp-mcp

by WYRE-AI

cipp_reset_password

DestructiveIdempotent

⚠ HIGH-IMPACT. Resets a user's password, invalidating their current password. CIPP always generates the new password itself (a caller cannot choose one) and returns it in the response, or a PWPush link if PWPush is enabled in CIPP, so…

Instructions

⚠ HIGH-IMPACT. Resets a user's password, invalidating their current password. CIPP always generates the new password itself (a caller cannot choose one) and returns it in the response, or a PWPush link if PWPush is enabled in CIPP, so treat the response as a secret. Optional mustChange (default false) sets forceChangePasswordNextSignIn so the user must change the password at next sign-in. The previous password cannot be restored; resetting again issues another new one. Confirm with the user before invoking.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "tenantFilter": "<tenantFilter>",
      "userId": "<userId>"
    },
    "name": "cipp_reset_password"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe target user's Azure AD object ID or User Principal Name (UPN, e.g. alice@contoso.com).
mustChangeNoWhen true, the user must change the password at next sign-in (CIPP MustChange / forceChangePasswordNextSignIn). Defaults to false.
tenantFilterYesTenant domain name or ID to scope the operation. Use 'allTenants' to target every managed tenant.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / mustChange
      Added value: +{
      +  "description": "When true, the user must change the password at next sign-in (CIPP MustChange / forceChangePasswordNextSignIn). Defaults to false.",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv1.11.1
    • removedInput schema / properties / newPassword
      Removed value: -{
      -  "description": "The replacement password to set. If omitted, a random password is generated and returned in the response.",
      -  "type": "string"
      -}
  3. Addedv1.7.0
  4. Removedv1.5.4
  5. First observedv0.1.0

TDQS

A4/5.0
Behavior2/5

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

The description discloses valuable details beyond the annotations — the caller cannot choose the password, CIPP generates and returns it (or a PWPush link when enabled), so the response is a secret, and the old password is unrecoverable. However, it conflicts with the supplied annotations: the annotation title says 'reversible' and idempotentHint is true, while the description states the previous password cannot be restored and that resetting again issues a different new password.

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 high-impact warning and the core action come first, followed by response-sensitivity, then the optional parameter, then the irreversibility note. It is dense rather than padded, though the last two sentences could be merged without losing anything.

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?

There is no output schema, and the description compensates by explaining exactly what the response contains (a generated password or a PWPush link) and how to treat it. For a two-required-parameter mutation tool, an agent has everything it needs to call this safely, apart from the annotation inconsistency noted above.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds real meaning: mustChange defaults to false and maps to forceChangePasswordNextSignIn, and no password parameter exists by design because CIPP always generates the value itself. That closes the most likely caller confusion about whether a password can be supplied.

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 opens with a specific verb and resource ('Resets a user's password, invalidating their current password'), which lets an agent distinguish this from cipp_reset_mfa and other account tools without opening any schema. The warning prefix and the mention of what's invalidated make the operation unmistakable.

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

Usage Guidelines4/5

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

It supplies a clear operating condition ('Confirm with the user before invoking') and a follow-on behavior ('resetting again issues another new one'), so an agent knows when to call it and what happens on repeat calls. It stops short of naming an alternative path and does not state preconditions such as required permissions.

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