Skip to main content
Glama
DingDawg Agent Spend Policy MCP

DingDawg Agent Spend Policy MCP

Official
by dingdawg

DingDawg Agent Spend Policy MCP

A small, local MCP server that deterministically evaluates whether a proposed agent spend action matches a supplied policy.

It returns one of ELIGIBLE, DENY, or STEP_UP, with a stable reason code. ELIGIBLE is local policy evidence only. It is not payment authorization.

Safety boundary

This package does not hold funds, private keys, payment credentials, customer data, or settlement authority. It does not sign, send, settle, custody, or record payments. It makes no network requests.

A production payment adapter needs separate, independently verified controls for authenticated policy/action provenance, canonical payload hashing, durable atomic budget reservation and replay protection, customer-controlled signing, rail validation, and settlement reconciliation.

Related MCP server: dingdawg-agent-wallet

Install

npx -y @dingdawg/agent-spend-policy-mcp

Configure it as a local stdio MCP server:

{
  "mcpServers": {
    "dingdawg-agent-spend-policy": {
      "command": "npx",
      "args": ["-y", "@dingdawg/agent-spend-policy-mcp"]
    }
  }
}

Tool

evaluate_spend_policy accepts an evaluation time, a policy, a proposed action, and the already-spent amount. All money is passed as integer micro-unit strings, never JavaScript floating-point numbers.

The caller supplies the clock and already-spent value; therefore this tool is safe for dry runs and local evidence, not a replacement for a trusted payment or accounting system.

Agent contract

The versioned machine-readable contract is capabilities.json. It describes the only tool this package exposes, its required inputs, its three possible outcomes, and its non-negotiable safety boundary.

  • Transport: local stdio MCP

  • Tool: evaluate_spend_policy

  • Required inputs: evaluationTime, policy, action, and alreadySpentMicros

  • Outputs: ELIGIBLE, DENY, or STEP_UP, each with a stable reason code

  • Side effects: none

  • Credentials, payment execution, custody, signing, settlement, and network access: not supported

The manifest is package-source evidence for this release, not a promise of a hosted agent-discovery endpoint. ELIGIBLE remains local policy evidence only, not payment authorization.

Development

npm install
npm test
npm run pack:check

Available Tools

1 tool
evaluate_spend_policyEvaluate agent spend-policy eligibilityA
Read-onlyIdempotent

Deterministically evaluates a proposed action against caller-supplied policy. This is local policy evidence only: it never authorizes, signs, sends, settles, custodies, or records a payment.

Inputs: action (required), policy (required), evaluationTime (required), alreadySpentMicros (required). Returns: outcome, reasonCode

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of overlap or ambiguity. The tool's purpose is clearly defined and distinct.

    Naming Consistency5/5

    The sole tool name 'evaluate_spend_policy' follows a clear verb_noun pattern, and with no other tools, there are no inconsistent conventions.

    Tool Count4/5

    A single tool is slightly thin, but it is well-scoped for the server's narrow purpose of evaluating spend policies. The count is reasonable and not trivial.

    Completeness5/5

    The tool fully covers its domain: it deterministically evaluates a proposed action against policy and explicitly avoids out-of-scope actions. No obvious gaps exist for the stated purpose.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enforces deterministic policies on AI agent tool calls, evaluating actions against compliance modules (SOC 2, HIPAA, GDPR, etc.) and returning ALLOW, BLOCK, or CONSTRAIN decisions with an audit trail.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables agents to request payment authorization against signed human mandates, enforcing policy-as-code limits and returning a decision (authorize, challenge, or deny) without moving funds.
      1
      1
      Apache 2.0