// SCAN REPORT

Marqeta DiVA API MCP Server

26 tools. 3 can modify or destroy data without limits.

1 destructive tool with no built-in limits. Policy required.

Last updated: 4 Jul 2026

3 can modify or destroy data

23 read-only

26 tools total

Community server · catalogue entry verified 04/07/2026

How to control Marqeta DiVA API MCP Server ↓

TOOL MAP

What Marqeta DiVA API MCP Server exposes to your agents

Read (23) Write / Execute (2) Destructive / Financial (1)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Marqeta DiVA API MCP Server tools

Destructive · High clear_index This tool permanently removes all transaction data from the vector index without the ability to undo the action. Write · Medium export_view_to_file This tool creates and writes new files containing financial data exports (transactions, settlements, chargebacks, balances). Write · Medium index_transactions This tool reads transactions from the DiVA API and writes/indexes them into local storage systems (SQLite database and ChromaDB vector store).

3 of Marqeta DiVA API MCP Server's 26 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Marqeta DiVA API MCP Server

PolicyLayer is an MCP gateway — it sits between your AI agents and Marqeta DiVA API MCP Server, and nothing reaches the server without passing your rules. These are the rules we recommend:

Deny destructive operations

{
  "clear_index": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations

{
  "export_view_to_file": {
    "limits": [
      {
        "counter": "export_view_to_file_per_hour",
        "window": "hour",
        "max": 30,
        "scope": "grant"
      }
    ]
  }
}

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

{
  "find_similar_transactions": {
    "limits": [
      {
        "counter": "find_similar_transactions_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Marqeta DiVA API MCP Server — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON MARQETA DIVA API →

Instant setup, no code required.

FULL CATALOGUE

All 26 Marqeta DiVA API MCP Server tools

DESTRUCTIVE 1 tools

Destructive clear_index Clear all transactions from the vector index.

WRITE 2 tools

Write export_view_to_file Export datasets to a file (JSON or CSV). Note: DiVA API limits results to 10,000 records per query. Write index_transactions Sync transactions from DiVA to local storage (SQLite + ChromaDB).

READ 23 tools

Read find_similar_transactions Find transactions similar to a specific transaction. Read get_activity_balances Get cardholder-level balance data. Includes individual cardholder balances, Read get_activity_balances_network_detail Get activity balance data broken out by card network (Visa, Mastercard, Maestro, Cirrus, etc.). Read get_authorizations Get authorization transaction data. Includes authorization amounts, counts, Read get_card_counts Get card count metrics aggregated over time. Track cards in circulation, active cards, Read get_cards Get card detail data. Includes user tokens, card state, active status, and UAI. Read get_chargebacks_detail Get detailed chargeback information. Includes transaction dates/types and Read get_chargebacks_status Get chargeback status data. Includes chargeback state, tokens, and Read get_clearings Get clearing/reconciliation data. Provides accounting-level line items for Read get_declines Get declined transaction data. Includes transaction tokens, decline reasons, Read get_index_stats Get comprehensive statistics about local storage (SQLite + ChromaDB). Read get_loads Get load transaction data. Includes load amounts and transaction details. Read get_program_balances Get program-level balance data. Includes beginning/ending bank balances, Read get_program_balances_settlement Get settlement-based program balance data. Includes settlement balance information Read get_server_version Get the MCP server version to verify it has been restarted with latest code changes. Read get_settlements Get settlement transaction data. Includes transaction status, post dates, Read get_transaction_token Map Core API transaction tokens to DiVA report transaction tokens. Read get_user_counts Get user count metrics aggregated over time. Track users with accounts, suspended users, Read get_users Get user detail data. Includes user tokens, UAI, and number of physical/virtual cards. Read get_view_schema Get the schema definition for any view endpoint. Returns field names, Read list_available_views Get a list of all available DiVA API view endpoints with metadata. Read query_local_transactions Query transactions directly from local SQLite storage using filters. Read semantic_search_transactions Search transactions using natural language queries.

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Marqeta DiVA API MCP Server

Can an AI agent delete data through the Marqeta DiVA API MCP Server MCP server? +

Yes. The Marqeta DiVA API MCP Server server exposes 1 destructive tools including clear_index. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Marqeta DiVA API MCP Server? +

The Marqeta DiVA API MCP Server server has 2 write tools including export_view_to_file, index_transactions. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Marqeta DiVA API MCP Server.

How many tools does the Marqeta DiVA API MCP Server MCP server expose? +

26 tools across 3 categories: Destructive, Read, Write. 23 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Marqeta DiVA API MCP Server? +

Register the Marqeta DiVA API MCP Server MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Marqeta DiVA API MCP Server tool call.

Deterministic rules across all 26 Marqeta DiVA API MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON MARQETA DIVA API →

Instant setup, no code required.

26 Marqeta DiVA API MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.