Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_permission_revoke

Revoke a user's asset access or delete a permission rule; preview affected rules first, then confirm changes to avoid unintended access removal.

Instructions

Revoke a user's access to an asset, or delete an entire AssetPermission rule. Always call with confirm=false first to preview affected rules!

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

Input Schema

NameRequiredDescriptionDefault
ruleNoSpecific permission rule name or ID
userNoUser to remove from matching rule(s)
assetNoAsset to remove from matching rule(s)
confirmNoSet to true ONLY after explicit user confirmation.
delete_entire_ruleNoDelete the entire permission rule

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations supplied, the description carries the safety burden and does well: it flags a destructive mutation, a two-stage preview/confirm flow, and ties confirm=true to explicit user confirmation. It still omits whether deletion is reversible, what the preview returns, and what permissions are required to revoke.

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?

Two short sentences, front-loaded with the action and followed immediately by the critical safety instruction. The exclamation mark and the lack of separate clauses for the two modes are minor blemishes on an otherwise efficient definition.

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?

For a five-parameter destructive tool with no annotations and no output schema, the description covers the destructive risk and the confirm protocol but leaves the precedence between rule and user/asset undefined, and does not describe what the preview step returns. Adequate, but an agent would still have to guess on multi-parameter combinations.

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 100%, so the schema already documents all five parameters, including the confirm and delete_entire_rule flags. The description adds only the preview/confirm sequencing; it never explains how rule interacts with user/asset when several are supplied, which is the main ambiguity an agent would hit.

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 a specific verb+resource ('Revoke a user's access to an asset') and names the second mode ('delete an entire AssetPermission rule'), which implicitly separates it from the jms_permission_grant sibling. It is clear what the tool does, though the two modes are packed into one sentence without labels.

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 gives an explicit workflow rule: always call with confirm=false first to preview affected rules, then presumably confirm. It does not name alternatives (e.g., jms_permission_grant or jms_permissions_list) or say when to prefer rule-level versus user/asset-level revocation, so the routing guidance is partial.

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