// SCAN REPORT

Braintree MCP Server

4 tools. 2 can modify or destroy data without limits.

2 write tools that can modify data. Rate limits recommended.

Last updated: 29 Jun 2026

2 can modify or destroy data

2 read-only

4 tools total

Community server · catalogue entry verified 29/06/2026

How to control Braintree MCP Server ↓

TOOL MAP

What Braintree MCP Server exposes to your agents

Read (2) Write / Execute (2) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Braintree MCP Server tools

Execute · Critical braintree_execute_graphql This tool executes GraphQL queries against Braintree's payment API. Execute · Critical braintree_execute_graphql_sse GraphQL execution on a payment processor with access to transactions, payments, and customer data represents a critical Execute risk.

2 of Braintree MCP Server's 4 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Braintree MCP Server

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

Cap read operations

{
  "braintree_ping": {
    "limits": [
      {
        "counter": "braintree_ping_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 Braintree 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 BRAINTREE →

Instant setup, no code required.

FULL CATALOGUE

All 4 Braintree MCP Server tools

EXECUTE 2 tools

Execute braintree_execute_graphql braintree_execute_graphql Execute braintree_execute_graphql_sse braintree_execute_graphql_sse

READ 2 tools

Read braintree_ping Performs a simple ping query to the Braintree GraphQL API to check connectivity and authentication. Read braintree_sse_ping Performs a simple ping query to the Braintree GraphQL API to check connectivity and authentication.

EXPLORE

Related servers

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

FAQ

Questions about Braintree MCP Server

Is the Braintree MCP Server MCP server safe to use without restrictions? +

The Braintree MCP Server server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Braintree MCP Server MCP server expose? +

4 tools across 2 categories: Execute, Read. 2 are read-only. 2 can modify, create, or delete data.

How do I enforce a policy on Braintree MCP Server? +

Register the Braintree 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 Braintree MCP Server tool call.

Deterministic rules across all 4 Braintree MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON BRAINTREE →

Instant setup, no code required.

4 Braintree MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.