Assess the risk of deposit/funding transactions. Use this when a user is transferring funds to a wallet address on your platform and you need to evaluate the risk level of the source of funds. This traverses all addresses in the funding source direction. Supported Chains: Same as get_address_risk...
Risk signalsHandles credentials or secrets (token)
Part of the Kyt server.
Free to start. No card required.
AI agents call get_deposit_transaction_risk to retrieve information from Kyt without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_deposit_transaction_risk only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_deposit_transaction_risk": {}
}
}See the full Kyt policy for all 3 tools.
These attack patterns abuse exactly the kind of access get_deposit_transaction_risk gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Assess the risk of deposit/funding transactions. Use this when a user is transferring funds to a wallet address on your platform and you need to evaluate the risk level of the source of funds. This traverses all addresses in the funding source direction. Supported Chains: Same as get_address_risk (Full Query and Basic Query chains). Use this when: Evaluating incoming transactions to your platform, checking the risk level of fund sources, tracing the origin of deposits. Token parameter: For non-native tokens (USDT, USDC, etc.), provide the token contract address. For native tokens (ETH, BTC, SOL), use the token name instead. Returns: risk scores (0-100), risk levels (Severe/High/Medium/Low), list of detected risks with entity names, hop counts, exposure types (Direct/Indirect), and fund amounts/ratios.. It is categorised as a Read tool in the Kyt MCP Server, which means it retrieves data without modifying state.
Register the Kyt MCP server in PolicyLayer and add a rule for get_deposit_transaction_risk: 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 Kyt. Nothing to install.
get_deposit_transaction_risk 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 get_deposit_transaction_risk 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 get_deposit_transaction_risk. 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.
get_deposit_transaction_risk is provided by the Kyt MCP server (@starstar214/kyt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Kyt tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.