Transfer RTC tokens between wallets (requires Ed25519 signature). Args: from_address: Source wallet address (RTC address) to_address: Destination wallet address amount_rtc: Amount to transfer in RTC signature: Ed25519 hex signature of the transaction public_key: Ed25519 hex public key of the send...
AI agents use rustchain_transfer_signed to commit financial operations through RustChain + BoTTube MCP Server — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool moves cryptocurrency (RTC tokens) between wallets, which is a direct financial transaction. Even though it requires cryptographic signatures for authentication, it commits financial obligations and transfers value. The critical severity reflects the high blast radius: an AI agent with access to valid signed transactions could drain wallets or transfer funds to attacker-controlled addresses.
From the tool's definition Tool description explicitly states: "Transfer RTC tokens between wallets" and "Transfers require valid Ed25519 signatures for security." The function name contains "transfer" and accepts parameters like from_address, to_address, amount_rtc, and signature.
Documented attack patterns abuse exactly the kind of access rustchain_transfer_signed gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and RustChain + BoTTube MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for rustchain_transfer_signed:
{
"version": "1",
"default": "deny",
"tools": {
"rustchain_transfer_signed": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
}Any call to rustchain_transfer_signed is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Transfer RTC tokens between wallets (requires Ed25519 signature). Args: from_address: Source wallet address (RTC address) to_address: Destination wallet address amount_rtc: Amount to transfer in RTC signature: Ed25519 hex signature of the transaction public_key: Ed25519 hex public key of the sender memo: Optional memo/note for the transaction Returns transfer result with transaction ID and new balance. Transfers require valid Ed25519 signatures for security. It is categorised as a Financial tool in the RustChain + BoTTube MCP Server MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the RustChain + BoTTube MCP Server MCP server in PolicyLayer and add a rule for rustchain_transfer_signed: 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 RustChain + BoTTube MCP Server. Nothing to install.
rustchain_transfer_signed 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 rustchain_transfer_signed 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 rustchain_transfer_signed. 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.
rustchain_transfer_signed is provided by the RustChain + BoTTube MCP Server MCP server (scottcjn/rustchain-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 39 RustChain + BoTTube MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
39 RustChain + BoTTube MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.