Vote on parameters for an Automated Market Maker (AMM)
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.
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)
Documented attack patterns abuse exactly the kind of access amm-vote gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Xrpl mcp, and nothing reaches the server without passing your rules. This is the rule we recommend for amm-vote:
{
"version": "1",
"default": "deny",
"tools": {
"amm-vote": {
"limits": [
{
"counter": "amm-vote_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} 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.
Free to start. No card required.
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.
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.
amm-vote is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
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.
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.
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.
Start from Xrpl mcp, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
71 Xrpl mcp tools catalogued and risk-classified — across an index of 43,000+ MCP servers.