Request free KTA tokens from the Keeta test network faucet. Only works on the test network. Sends 5 KTA to the given address for development/testing. KTA is needed for transaction fees on the network. Returns: { status, address, amountRequested, currentBalance }
AI agents use keeta_request_test_tokens to commit financial operations through Keeta Network MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves tokens (KTA) to a specified address, which is a financial transfer operation. However, it is restricted to the test network and uses free/valueless test tokens, so real financial risk is minimal. The Financial category still applies as it involves token disbursement mechanics, but severity is medium rather than critical given the test-only constraint and fixed small amount (5 KTA).
From the tool's definition 'Request free KTA tokens from the Keeta test network faucet', 'Sends 5 KTA to the given address'
Attacks that exploit this kind of access
Request free KTA tokens from the Keeta test network faucet. Only works on the test network. Sends 5 KTA to the given address for development/testing. KTA is needed for transaction fees on the network. Returns: { status, address, amountRequested, currentBalance }. It is categorised as a Financial tool in the Keeta Network MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Keeta Network MCP Server MCP server in PolicyLayer and add a rule for keeta_request_test_tokens: 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 Keeta Network MCP Server. Nothing to install.
keeta_request_test_tokens 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 keeta_request_test_tokens 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 keeta_request_test_tokens. 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.
keeta_request_test_tokens is provided by the Keeta Network MCP Server MCP server (schenkty/kta-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 →