Assess the risk of withdrawal/outgoing transactions. Use this when there is an outgoing transaction and you need to conduct a risk assessment of the destination of the funds. Evaluates counterparties involved in the asset destination. Supported Chains: Same as get_address_risk (Full Query and Ba...
Handles credentials or secrets (token)
Part of the Kyt MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_withdraw_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_withdraw_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.
tools:
get_withdraw_transaction_risk:
rules:
- action: allowSee the full Kyt policy for all 3 tools.
Agents calling read-class tools like get_withdraw_transaction_risk have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Assess the risk of withdrawal/outgoing transactions. Use this when there is an outgoing transaction and you need to conduct a risk assessment of the destination of the funds. Evaluates counterparties involved in the asset destination. Supported Chains: Same as get_address_risk (Full Query and Basic Query chains). Use this when: Evaluating outgoing transactions from your platform, checking the risk level of fund destinations, compliance checks before sending funds. 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.
Add a rule in your Intercept YAML policy under the tools section for get_withdraw_transaction_risk. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Kyt MCP server.
get_withdraw_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_withdraw_transaction_risk rule in your Intercept 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 Intercept policy for get_withdraw_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_withdraw_transaction_risk is provided by the Kyt MCP server (@starstar214/kyt-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept