AI agents use stellar_fund_account to commit financial operations through Stellar MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves funds (test XLM) into an account on the Stellar network. While it operates on a test network (Friendbot is a testnet faucet), it commits a financial operation — transferring assets to an account. On testnet the blast radius is limited since funds have no real monetary value, hence medium severity rather than high/critical.
From the tool's definition Fund a test account using the Friendbot
Documented attack patterns abuse exactly the kind of access stellar_fund_account gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Stellar MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for stellar_fund_account:
{
"version": "1",
"default": "deny",
"tools": {
"stellar_fund_account": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to stellar_fund_account is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Fund a test account using the Friendbot. It is categorised as a Financial tool in the Stellar MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Stellar MCP server in PolicyLayer and add a rule for stellar_fund_account: 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 Stellar MCP. Nothing to install.
stellar_fund_account is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stellar_fund_account 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 stellar_fund_account. 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.
stellar_fund_account is provided by the Stellar MCP server (syronlabs/stellar-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Stellar 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.
12 Stellar MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.