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

WHAT IT DOES

What build_add_liquidity does on CSPR[dot]trade MCP

AI agents invoke build_add_liquidity 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_add_liquidity needs a policy

build_add_liquidity triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

build_add_liquidity Rate-limited

build_add_liquidity 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_add_liquidity": {
      "limits": [
        {
          "counter": "build_add_liquidity_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_add_liquidity

What does the build_add_liquidity tool do? +

Build an unsigned add-liquidity transaction for a token pair. 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_add_liquidity? +

Register the CSPR[dot]trade MCP server in PolicyLayer and add a rule for build_add_liquidity: 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_add_liquidity? +

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

Can I rate-limit build_add_liquidity? +

Yes. Add a rate_limit block to the build_add_liquidity 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_add_liquidity completely? +

Set action: deny in the PolicyLayer policy for build_add_liquidity. 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_add_liquidity? +

build_add_liquidity 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.