build_swap · CSPR[dot]trade MCP: Risk & Policy

WHAT IT DOES

What build_swap does on CSPR[dot]trade MCP

AI agents invoke build_swap to trigger actions in CSPR[dot]trade MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why build_swap needs a policy

This tool triggers an external financial operation (token swap) whose effects directly depend on the arguments provided (token pairs, amounts, slippage settings, etc.). Although the transaction is 'unsigned' and requires external signing to finalize, the tool constructs the binding financial instruction.

From the tool's definition 'Build an unsigned swap transaction' on a decentralized exchange (CSPR.trade) that constructs a financial operation (swap/trade).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_swap Rate-limited

build_swap stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "build_swap": {
      "limits": [
        {
          "counter": "build_swap_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches CSPR[dot]trade MCP, so you can run agents against it safely.

FAQ

Questions about build_swap

What does the build_swap tool do? +

Build an unsigned swap transaction. Returns the deploy JSON for external signing, plus a human-readable summary. It is categorised as a Execute tool in the CSPR[dot]trade MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on build_swap? +

Register the CSPR[dot]trade MCP server in PolicyLayer and add a rule for build_swap: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches CSPR[dot]trade MCP. Nothing to install.

What risk level is build_swap? +

build_swap is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit build_swap? +

Yes. Add a rate_limit block to the build_swap rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block build_swap completely? +

Set action: deny in the PolicyLayer policy for build_swap. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides build_swap? +

build_swap is provided by the CSPR[dot]trade MCP server (make-software/cspr-trade-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

build_swap is one line of CSPR[dot]trade's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →