Skip to main content
Glama
Zw-awa

ssh-session-mcp

by Zw-awa

ssh-session-policy-upsert

Upsert custom policy rules for SSH sessions to block, warn, or log commands matching JavaScript regex patterns.

Instructions

Add or update a session-level custom policy rule. Session rules are applied after immutable built-in hard blocks and before the built-in safe/full warning set.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesStable rule id used for future updates or removal
modeNoWhich operation mode the rule applies to
flagsNoOptional JavaScript regex flags, for example i or gi
actionYeserror blocks the command, warning allows it with warning metadata, log only annotates it
enabledNoWhether the rule is active. Defaults to true
messageYesHuman-readable reason shown when the rule matches
patternYesJavaScript regular expression source without surrounding slashes
sessionNoSession id, session ref, or session name. Defaults to the active session
categoryYesRule category shown in blocked/warned responses
priorityNoLower numbers run earlier within the same severity band
suggestionNoOptional remediation hint shown alongside the message
Behavior3/5

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

No annotations; description adds context about rule application order (after hard blocks, before warnings) but lacks details on side effects, authentication needs, or whether updates affect existing sessions.

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?

Two sentences, front-loaded with action, no wasted words.

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 but leaves gaps: no output schema, no default for 'mode', no explanation of return value. For 11 parameters, additional context on update behavior would help.

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 description adds no further parameter meaning beyond what schema provides. Baseline score of 3 applies.

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?

Description clearly states 'Add or update a session-level custom policy rule' with specific verb and resource, and distinguishes the rule's position relative to other policy layers.

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?

Implies usage via rule ordering but does not explicitly state when to use vs alternatives like ssh-session-policy-list or ssh-session-policy-reset. No guidance on when to add vs update.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Zw-awa/ssh-session-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server