approval-guardian
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 |
|---|---|
| check_approvalsA | Audit a wallet's ACTIVE ERC-20 token approvals (allowances) for drain risk — the #1 way DeFi wallets get emptied. Pulls every Approval event the wallet ever emitted, reads the LIVE allowance for each (token, spender) pair, classifies the spender (EOA / unknown contract / upgradeable proxy / known router) and returns a prioritized CLEAN / REVIEW / AT_RISK verdict listing exactly which approvals to revoke first — with the approve(spender,0) revoke calldata ready to sign. Read-only; never moves funds, never holds a key. Use this before/after a wallet interacts with unfamiliar dApps, when a user fears a drainer, or to harden any wallet. Chains: ethereum, base, bsc, polygon, arbitrum. |
| revoke_planA | Return ONLY the revoke action plan for a wallet: the ordered list of risky approvals to cancel, each with the token, spender and the exact approve(spender,0) calldata the user signs to revoke it. Use after check_approvals to get a clean, signable to-do list. Read-only; the user signs each revoke themselves. |
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 2 tools
The two tools have distinct and complementary purposes: check_approvals performs an audit and provides a verdict, while revoke_plan generates a list of revoke actions. There is no overlap in functionality.
Both tool names follow a consistent verb_noun pattern: check_approvals and revoke_plan, making them predictable and easy to understand.
With only 2 tools, the server is minimal but well-scoped for its specific purpose of auditing and planning revocations. It covers the essential operations without unnecessary bloat.
The tools cover the core workflow of auditing approvals and generating a revocation plan. The lack of a tool for executing revocations is intentional (read-only design), so the surface is complete for its stated domain.