AI agents call list_outgoing_transfers to retrieve information from Run402 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of pending transfers that have been initiated by the authenticated user. It retrieves and displays data without creating, modifying, deleting, or executing any operations. The blast radius is minimal—an AI agent calling this tool would only gain visibility into the user's own outgoing transfer requests, which are already authorized by that wallet.
From the tool's definition Tool name is 'list_outgoing_transfers' and description states 'List pending project transfers INITIATED BY the authenticated wallet'. The verb 'List' indicates a retrieval operation with no modification or side effects.
Attacks that exploit this kind of access
List pending project transfers INITIATED BY the authenticated wallet (v1.59+). Each entry carries. It is categorised as a Read tool in the Run402 MCP Server, which means it retrieves data without modifying state.
Register the Run402 MCP server in PolicyLayer and add a rule for list_outgoing_transfers: 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.
list_outgoing_transfers is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_outgoing_transfers 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 list_outgoing_transfers. 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.
list_outgoing_transfers 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 →