jamjet-policy
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| policy_evaluateA | Evaluate the currently loaded JamJet policy against a candidate MCP tool name. Returns the matched rule, the decision (allow / block / require_approval / audit), and the matched glob pattern. Use this to dry-run a tool call before issuing it, or to explain why a previous call was blocked. Read-only and side-effect free — does not write to the audit log. |
| policy_list_rulesA | List every rule in the currently loaded JamJet policy, in declaration order. Each entry includes the rule index, action (allow / block / require_approval / audit), and the glob pattern it matches. Use this to inspect the active policy without reading the YAML file directly, or to verify a rollout placed rules in the expected order. Read-only. |
| policy_load_infoA | Report the path to the policy file currently loaded by this server, plus the number of rules it contains and the policy schema version. Use this once at session start to confirm the server has the expected policy attached. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: evaluate a specific tool against policy, list all rules, and report loaded policy info. No overlap between them.
All tools follow the consistent pattern 'policy_verb[_noun]' using snake_case, making them predictable and easy to understand.
With 3 tools, the server is tightly scoped to policy inspection and evaluation, fitting its purpose well without unnecessary bloat.
The set covers the essential operations for a read-only policy server: evaluating a candidate, inspecting rules, and confirming the loaded policy. No missing functionality for its intended use.