Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_permission_grant

Grants JumpServer users or user groups access to assets or nodes, with account, action, and expiry options. Run with confirm=false to preview accounts and require explicit approval before confirming.

Instructions

Grant a JumpServer User (or User Group) access to an Asset (or Node). Always run with confirm=false first to preview available accounts on the asset, ask the user which account (root/ubuntu/@ALL), actions (connect/transfer/all), and expiry duration they want, and only set confirm=true after explicit user approval.

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_grant"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoOptional temporary access duration in days
nodeNoTarget asset tree node (name or ID)
userNoTarget user (username, name, or ID)
assetNoTarget server asset (name, IP, or ID)
hoursNoOptional temporary access duration in hours
actionsNoAllowed session actions: 'connect', 'readonly', 'transfer', 'all', or comma-separated ('connect,upload,download,copy,paste')connect
commentNo
confirmNoSet to true ONLY after explicit user confirmation.
accountsNoComma-separated system account usernames (e.g. 'root', 'ubuntu', 'root,ubuntu', or '@ALL')@ALL
rule_nameNoOptional existing or custom permission rule name
user_groupNoTarget User Group (name or ID)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.2/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose the most consequential trait — that the tool is a two-phase mutation with a preview mode gated on confirm. It does not cover permission requirements, what happens if a matching rule already exists (rule_name collision), or how days and hours combine, leaving real behavioral gaps for an 11-param mutation.

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 sentences, purpose front-loaded, then the workflow. The second sentence is long and bundles several instructions, but nothing is wasted and no filler is present.

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?

Adequate for a mutation tool with no output schema and no annotations: the confirm workflow is covered. However, with 11 optional parameters and zero required, it does not explain how asset vs node, user vs user_group, or days vs hours should be chosen or combined, nor what the preview actually returns, which an agent needs to call it confidently.

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 91%, so the schema already documents every parameter including accounts (@ALL), actions, and confirm. The description repeats those same examples rather than adding new meaning, though it does usefully frame which parameters must be negotiated with the user.

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 — grant access from a JumpServer User/User Group to an Asset/Node — and the pairing of grantable and target entities is explicit. The 'grant' verb also cleanly separates it from the jms_permission_revoke sibling without needing to name it.

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 an explicit operating procedure: always call with confirm=false first to preview accounts, gather the account, actions, and expiry from the user, and only then set confirm=true after explicit approval. This is exactly the when/when-not guidance an agent needs for a two-phase mutation.

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