Skip to main content
Glama
vbr-write-mcp

vbr-write-mcp

by Aquatick

Manage User Security

manage_user_security
Destructive

Reset a user's MFA enrollment or enable/disable service-account mode to enforce MFA for people while exempting automation accounts.

Instructions

Reset a user's MFA (they must enroll again at next login), or switch the service-account mode (service accounts are exempt from MFA - use for automation accounts only). Roles: update_object(kind='user').

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": {
      "user_id": "<user_id>",
      "action": "<action>"
    },
    "name": "manage_user_security"
  }
}

Input Schema

NameRequiredDescriptionDefault
actionYes
user_idYes
confirm_tokenNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and non-idempotent, so the bar is lower; the description still adds genuine consequence detail — the user must re-enroll at next login, and service accounts bypass MFA entirely. What it omits is the confirm_token flow, which matters for a destructive action.

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 operations are front-loaded and the parentheticals earn their space by explaining side effects. The closing 'Roles: `update_object(kind='user')`' is a cryptic fragment that adds ambiguity rather than information.

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

Completeness3/5

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

An output schema exists, so return values need no explanation. For a destructive three-parameter mutation with zero schema coverage, the description covers the action branches and their consequences but leaves the confirmation parameter and required permissions undocumented.

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

Parameters2/5

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

Schema description coverage is 0%, so the description carries the full burden. It explains the meaning of the action enum branches reasonably well, but says nothing about user_id semantics or, more importantly, what confirm_token is and when it is required for a destructive mutation.

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

Purpose4/5

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

The description states two concrete operations on a specific resource: resetting a user's MFA and toggling service-account mode, both scoped to a user. That is far more specific than the title. The trailing fragment 'Roles: `update_object(kind='user')`' is opaque and doesn't cleanly distinguish this tool from the update_object sibling.

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

Usage Guidelines3/5

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

It gives real usage guidance for one branch ('use for automation accounts only') and warns that service accounts are MFA-exempt, which implies caution. However, it never says when to prefer this tool over update_object or other user-management siblings, and there is no explicit when-not guidance for the MFA reset path.

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