Skip to main content
Glama
MvikManners

aw1-circuit-breaker

by MvikManners
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
intercept_tool_callB
Intercept and evaluate an autonomous AI agent tool execution payload before runtime invocation.
Determines whether the execution is safe or requires immediate containment.

Args:
    actor_id: Unique identifier or name of the calling agent, user, or process.
    tool_name: The target tool, environment, or command type (e.g., 'bash', 'sql', 'python', 'eval').
    payload: The raw code, shell command, query, or parameters to be inspected by the circuit breaker.

Returns:
    Dictionary containing the security verdict ('PERMITTED' or 'HALT_AND_CONTAIN'),
    authorization status, cryptographic execution token (if permitted), risk score,
    and detected AST primitives.
analyze_code_astA
Deconstruct source code or commands into abstract syntax tree (AST) primitives to detect dangerous patterns.
Identifies dynamic evaluations, shell piping, lateral network egress, and destructive operations.

Args:
    code: The source code snippet, query, or command string to statically analyze.
    environment: The syntactic context or execution environment ('python', 'bash', 'sql'). Default is 'python'.

Returns:
    Dictionary containing detected execution primitives, security classification, and containment recommendations.
get_circuit_breaker_telemetryB
Retrieve operational status, active defense policies, and telemetry for the AW-1 Circuit Breaker.

Returns:
    Dictionary with engine version, status, registered containment layers, and SLA guarantees.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.6/5.0

Scored across 3 tools

Disambiguation4/5

Each tool has a recognizable role: get_circuit_breaker_telemetry reads status, intercept_tool_call gates a runtime execution, and analyze_code_ast performs static analysis. However, intercept_tool_call and analyze_code_ast overlap, since both inspect payloads and both return detected AST primitives/risk, so an agent may hesitate between them.

Naming Consistency5/5

All three names use a consistent snake_case verb_noun pattern (get_..., intercept_..., analyze_...). The convention is predictable and readable across the set.

Tool Count4/5

Three tools is at the low end but reasonable for a focused circuit breaker: status, enforcement, and analysis. It is slightly thin, with no tools for adjacent concerns like policy management or audit history.

Completeness3/5

The core inspect/enforce/observe lifecycle is covered, but the telemetry tool references 'active defense policies' and 'containment layers' with no tool to list, create, or update those policies, and there is no audit/decision-log retrieval. These are notable gaps for a security-gateway domain.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources