Request funds (useful for testing/development)
AI agents use REQUEST_FUNDS to commit financial operations through Solana MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves or solicits cryptocurrency funds, placing it in the Financial category. Even if intended for testnet/devnet faucets, it commits a financial operation (requesting token transfers). On mainnet or if misconfigured, misuse could drain faucets or request real assets. Severity is high due to the financial blast radius on a blockchain platform that also supports mainnet operations.
From the tool's definition "Request funds" — explicitly requests funds (cryptocurrency/tokens) from a faucet or external source; part of a Solana blockchain server with financial operations like TRADE and TRANSFER
Attacks that exploit this kind of access
Request funds (useful for testing/development). It is categorised as a Financial tool in the Solana MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Solana MCP Server MCP server in PolicyLayer and add a rule for REQUEST_FUNDS: 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 Solana MCP Server. Nothing to install.
REQUEST_FUNDS 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 REQUEST_FUNDS 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 REQUEST_FUNDS. 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.
REQUEST_FUNDS is provided by the Solana MCP Server MCP server (pingaifun/ping-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →