Skip to main content
Glama
AiJumpOps MCP Server

AiJumpOps MCP Server

by shariatissh

jms_security_audit

Scan JumpServer to identify users without MFA, overprivileged or expired permission rules, and unassigned assets so you can remediate access risks.

Instructions

AI Security Auditor: Scan JumpServer for users without 2FA/MFA, overprivileged permission rules (e.g. @ALL or root across broad nodes), expired rules, and unassigned assets.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations provided, the description carries the full disclosure burden. It does communicate that the tool performs multiple checks and returns findings rather than performing mutations, and it names concrete detection criteria (e.g. @ALL, root across broad nodes), which is real behavioral value. It does not state that it is read-only, whether it is expensive or slow, whether results are paginated or summarized, or what the report looks like.

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?

A single front-loaded sentence that puts the action and scope first, then the finding categories. The only waste is the "AI Security Auditor:" persona prefix, which adds no operational information an agent can act on.

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 zero-parameter audit tool with no output schema, the description tells the agent what categories of issues will be surfaced but not the shape, size, or structure of the returned report. It is adequate to decide to call the tool, but leaves the agent guessing about result format and whether all four checks always run.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies a whole-instance scan with no scoping inputs, which is consistent with the empty schema.

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?

States a specific verb ("Scan") and target (JumpServer) and enumerates the four finding categories it reports: users without 2FA/MFA, overprivileged permission rules, expired rules, and unassigned assets. This makes it clearly a composite posture audit rather than a single-resource list, distinguishing it from siblings like jms_users_list or jms_permissions_list. The leading "AI Security Auditor:" label is persona framing rather than additional specificity.

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?

The enumerated check categories imply when the tool is useful (security review of accounts, permissions, and asset assignment), but there is no explicit guidance on when to pick this over the granular list tools or on any prerequisites. Nothing says whether it should be run before acting on findings or how it relates to siblings such as jms_check_access.

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