mcp-azeth

azeth_get_guardrails

Check the guardian security configuration for a smart account, including spending limits, token and protocol whitelists, daily spend progress, and pending timelock changes.

Instructions

View the guardian security configuration for a smart account.

Use this when: You want to check spending limits, token/protocol whitelists, daily spend tracking, emergency withdrawal status, or pending guardrail changes.

Returns: Full guardian state including spending limits (USD), whitelisted tokens and protocols, daily spend progress, and any pending timelock changes.

This is read-only and safe to call at any time.

Example: { "smartAccount": "me" }

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "azeth_get_guardrails"
  }
}

Input Schema

Name	Required	Description	Default
`chain`	No	Target chain. Defaults to AZETH_CHAIN env var or "baseSepolia". Accepts "base", "baseSepolia", "ethereumSepolia", "ethereum" (and aliases like "base-sepolia", "eth-sepolia", "sepolia", "eth", "mainnet").
`smartAccount`	No	Smart account to inspect. Accepts address, "me", "#N", or account name. Defaults to first account.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.9Mar 24, 2026

TDQS

A4.2/5.0

Behavior4/5

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

No annotations provided, so description carries full burden. Explicitly states 'read-only and safe to call at any time'. Discloses return structure including 'pending timelock changes' which warns about pre-committed state. Doesn't mention auth requirements, but substantial behavioral coverage provided.

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?

Excellent structure: 1) Purpose, 2) When to use, 3) Return values, 4) Safety declaration, 5) Example. No wasted words; front-loaded with critical info. Sentence density is high with zero redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so describing return values ('Returns: Full guardian state...') is essential and present. Covers safety profile, parameter usage via example, and distinguishes from mutation tools. Could briefly mention relationship to azeth_guardian_status, but complete enough for safe invocation.

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% with detailed descriptions for both chain (including default fallback chain) and smartAccount (including 'me' shorthand). Description includes example usage reinforcing the 'me' pattern, but since schema already documents all semantics thoroughly, this meets the baseline.

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?

Clear specific verb 'View' + resource 'guardian security configuration'. Explicitly distinguishes from siblings like azeth_guardian_status (implied to return current status vs full configuration) and write operations like azeth_whitelist_token by focusing on security inspection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit 'Use this when:' section lists specific inspection scenarios (spending limits, whitelists, daily tracking). Clearly indicates appropriate contexts. Lacks explicit named alternatives or 'do not use when' guidance, but use cases are specific enough to guide selection.

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

Deploy Server