Arai
Server 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 |
|---|---|
| arai_add_guardA | Register a new guardrail that Ārai will enforce on subsequent tool calls. Use when you discover a rule mid-session that should persist for the rest of this project (e.g. 'never write to /etc', 'always run tests before push'). The rule is parsed the same way CLAUDE.md instructions are and stored locally — it takes effect on the very next PreToolUse hook. |
| arai_list_guardsA | List currently active guardrails, optionally filtered by a substring. Returns subject/predicate/object triples plus their source files so the agent can see what constraints are live before making a tool call. |
| arai_check_actionA | Probe whether a hypothetical tool call would match any active guardrail — without executing the call or writing to the audit log. Use BEFORE taking an action you think might be regulated to avoid a deny-and-retry loop. Returns matched rules with severity (block / warn / inform) and source file:line, exactly the same shape |
| arai_recent_decisionsA | Look up the most recent guardrail decisions Ārai has emitted in this session (or any session if |
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 4 tools
Each tool has a unique and clear purpose: adding guardrails, probing actions, listing guards, and reviewing decisions. No overlap exists.
All tools follow the consistent 'arai_verb_noun' pattern, using snake_case throughout. Names are descriptive and predictable.
With 4 tools, the set is appropriately scoped for a guardrail management server—neither too few nor too many.
The tools cover the core lifecycle (add, check, list, review) but lack a removal or update mechanism for guardrails, which is a minor gap.