AI agents use request_faucet to commit financial operations through Run402 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
The tool moves cryptocurrency (testnet USDC) to the requester, which constitutes a financial transaction even though it's on a test network. While testnet tokens have no real monetary value, the tool interacts with blockchain financial infrastructure, triggers on-chain transfers, and is rate-limited precisely because it has resource costs. It fits the Financial category as the most severe applicable.
From the tool's definition Request free testnet USDC from the Run402 faucet (Base Sepolia)... Returns 0.25 USDC
Attacks that exploit this kind of access
Request free testnet USDC from the Run402 faucet (Base Sepolia). Rate limit: 1 per IP per 24h. Returns 0.25 USDC — enough for 2 prototype databases. It is categorised as a Financial tool in the Run402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for request_faucet: 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 Run402. Nothing to install.
request_faucet 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_faucet 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_faucet. 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_faucet is provided by the Run402 MCP server (kychee-com/run402). 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 →