aw1-circuit-breaker
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| inspect_python_codeB | Deconstructs and analyzes Python code AST for unsafe constructs, shell injection, dynamic evaluation, and socket egress. |
| inspect_tool_argumentsC | Validates arguments passed to external tools for risky shell patterns, eval triggers, or socket connections. |
| get_containment_statusB | Returns the current state of zero-trust AST containment rules. |
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
The three tools target clearly distinct objects: Python source code, external tool arguments, and containment-rule status. An agent can readily distinguish when to inspect code versus arguments versus check status.
All names use consistent snake_case with a verb_noun pattern: inspect_python_code, inspect_tool_arguments, get_containment_status. The mix of inspect_* and get_* is predictable and semantically appropriate.
Three tools is a focused, reasonable surface for a circuit-breaker-style security server. It is slightly thin, but each tool has a clear role and no obvious redundancy.
The server covers inspection and status reporting, but it lacks operations to configure, update, or reset the zero-trust containment rules. This is a notable gap if the server is meant to manage containment policy rather than only observe it.