DingDawg Agent Spend Policy MCP
OfficialThis server provides a single local tool, evaluate_spend_policy, to deterministically check whether a proposed agent spend action is permitted under a caller-supplied policy. It returns one of three eligibility verdicts: ELIGIBLE, DENY, or STEP_UP with stable reason codes. The policy checks include matching expected principal, agent, authority, asset, payload hash, and idempotency key; verifying the rail and recipient are in allowed lists; enforcing per-action and daily limits using caller-supplied already-spent amount; optional step-up threshold and purpose requirement; and action expiration. All monetary values are integer micro-unit strings. The tool is read-only, idempotent, makes no network requests, has no side effects, and does not authorize, sign, send, settle, or execute any payment — it only provides a local policy evidence verdict.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@DingDawg Agent Spend Policy MCP Can I spend $50 on cloud compute? Check against our policy."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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-mcpConfigure 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_policyRequired inputs:
evaluationTime,policy,action, andalreadySpentMicrosOutputs:
ELIGIBLE,DENY, orSTEP_UP, each with a stable reason codeSide 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:checkAvailable Tools
1 toolevaluate_spend_policyEvaluate agent spend-policy eligibilityARead-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
Scored across 1 tool
With only one tool, there is no possibility of overlap or ambiguity. The tool's purpose is clearly defined and distinct.
The sole tool name 'evaluate_spend_policy' follows a clear verb_noun pattern, and with no other tools, there are no inconsistent conventions.
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.
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
Deterministic allow/require_approval/deny verdicts for agent actions, before they happen.
Score a planned spend before an agent pays. Verdicts: approve, ask_human, or block.
Check a proposed agent action against operator's rules: permit, deny or escalate, with the clause.
Advisory policy preflight for AI-agent spend requests; never executes payments or accesses wallets.
Related MCP Servers
AlicenseNot gradedqualityDmaintenanceEnforces 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- FlicenseNot gradedqualityDmaintenanceProvides MCP tools to enforce spend policies (allow, deny, step-up, allowlist) on agent wallets with an immutable audit trail.-
- AlicenseNot gradedqualityDmaintenanceEnables verification of AI agent identity, authority, and integrity at transaction time, returning signed verdicts for allow, step-up, review, or block.MIT
- AlicenseAqualityDmaintenanceEnables 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.11Apache 2.0