micro-mcp

Overview Schema Source Related Servers Discussions Admin

Revoke Micro app-user sessions

micro_user_sessions_revoke

DestructiveIdempotent

Revoke all active sessions and private download grants for a specific app user without disabling the account. Use this to terminate access across devices and secure user data when needed.

Instructions

Revoke every active session and private download grant for one explicit app user without disabling the 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": "<user>",
      "confirm": "<confirm>"
    },
    "name": "micro_user_sessions_revoke"
  }
}

Input Schema

Name	Required	Description
`path`	No	Micro project directory; defaults to the server working directory
`user`	Yes
`confirm`	Yes	Explicit confirmation that this app user's active sessions should be revoked

Output Schema

Name	Required	Description	Default
`ok`	Yes
`json`	No
`stderr`	Yes
`stdout`	Yes
`command`	Yes
`exitCode`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.5.1Aug 30, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already carry destructiveHint and idempotentHint; the description adds useful behavioral detail about exactly what is revoked and what is preserved. There is no contradiction with annotations, and the non-disabling guarantee is meaningful context beyond structured metadata.

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

Conciseness5/5

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

The description is a single, tightly worded sentence with no filler. It front-loads the action and scope, and every clause adds necessary information.

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?

Given the rich annotations (destructive, idempotent, open-world), an output schema, and the schema-covered confirmation parameter, the description is complete for tool selection and invocation. It states the action, target, extent, and non-effect clearly without needing to repeat structured fields.

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?

Schema coverage is 67%; path and confirm have descriptions, while user has only format/pattern. The description clarifies that the target is 'one explicit app user', adding some meaning to the user parameter, but it does not clarify confirm or path beyond what the schema already states.

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 states an explicit action ('Revoke'), precise scope ('every active session and private download grant'), and a clear boundary ('one explicit app user ... without disabling the user'). It distinguishes the tool from siblings like micro_user_disable and micro_private_grant_revoke without needing to open schemas.

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?

The description gives clear context: call this when you need to revoke all sessions and private download grants for a single app user while preserving the user account. It includes a when-not signal ('without disabling the user'), though it does not explicitly name alternative sibling tools.

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

Deploy Server