List recent x402 top-up + debit transactions for a wallet. SIWX-ONLY: rejects API key, requires X-Sign-In-With-X (VENICE_SIWX_TOKEN). The wallet in the path must match the SIWX-authenticated wallet.
AI agents call venice_x402_transactions to retrieve information from Venice MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
While this tool retrieves financial transaction data (which could inform decisions), it only performs read operations on transaction history. The authentication requirement (SIWX-ONLY, wallet matching) and access control mitigates risk.
From the tool's definition Tool name 'venice_x402_transactions' and description 'List recent x402 top-up + debit transactions for a wallet' indicates retrieval of financial transaction history.
Documented attack patterns abuse exactly the kind of access venice_x402_transactions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Venice MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for venice_x402_transactions:
{
"version": "1",
"default": "deny",
"tools": {
"venice_x402_transactions": {}
}
} venice_x402_transactions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List recent x402 top-up + debit transactions for a wallet. SIWX-ONLY: rejects API key, requires X-Sign-In-With-X (VENICE_SIWX_TOKEN). The wallet in the path must match the SIWX-authenticated wallet. It is categorised as a Read tool in the Venice MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Venice MCP Server MCP server in PolicyLayer and add a rule for venice_x402_transactions: 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 Venice MCP Server. Nothing to install.
venice_x402_transactions 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 venice_x402_transactions 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 venice_x402_transactions. 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.
venice_x402_transactions is provided by the Venice MCP Server MCP server (veniceai/venice-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 27 Venice MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
27 Venice MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.