amm-vote

Vote on parameters for an Automated Market Maker (AMM)

SERVERXrpl mcp SOURCEromthpt/mcp-xrpl

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/romthpt-mcp-xrpl/amm-vote.md

WHAT IT DOES

What amm-vote does on Xrpl mcp

AI agents invoke amm-vote to trigger actions in Xrpl 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.

RISK

Why amm-vote is rated High

This tool submits a vote transaction to the XRP Ledger to influence AMM parameters (e.g., trading fees). It triggers an external on-chain operation with real effects on a live AMM pool. While it doesn't directly move funds or delete data, it executes a ledger transaction that can alter AMM behavior affecting all participants.

From the tool's definition Vote on parameters for an Automated Market Maker (AMM)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs amm-vote safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Xrpl mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For amm-vote, this is the rule to start with:

amm-vote Rate-limited

amm-vote 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": {
    "amm-vote": {
      "limits": [
        {
          "counter": "amm-vote_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Xrpl mcp, apply this rule, and every amm-vote call is checked against it from then on.

FAQ

Questions about amm-vote

What does the amm-vote tool do? +

Vote on parameters for an Automated Market Maker (AMM). It is categorised as a Execute tool in the Xrpl 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 amm-vote? +

Register the Xrpl MCP server in PolicyLayer and add a rule for amm-vote: 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 Xrpl mcp. Nothing to install.

What risk level is amm-vote? +

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

Can I rate-limit amm-vote? +

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

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

amm-vote is provided by the Xrpl MCP server (romthpt/mcp-xrpl). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Xrpl, and thousands of servers like it.

This server

All 71 Xrpl tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →