Return metadata for the cipher-solana-wallet-audit v1.4.0 ruleset — the free MIT GitHub Action that catches Solana wallet anti-patterns in CI: plaintext private keys (base58 OR hex), seed phrases (in comments OR string literals), Anchor.toml wallet leaks, Token2022 transfer-hook abuse, Drift-hack...
Risk signalsAdmin/system-level operation
Part of the CIPHER x402 — Paid Solana & Crypto Tools server.
Free to start. No card required.
AI agents call solana_wallet_security_audit_rules to retrieve information from CIPHER x402 — Paid Solana & Crypto Tools 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 solana_wallet_security_audit_rules 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": {
"solana_wallet_security_audit_rules": {}
}
}See the full CIPHER x402 — Paid Solana & Crypto Tools policy for all 15 tools.
These attack patterns abuse exactly the kind of access solana_wallet_security_audit_rules 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.
Return metadata for the cipher-solana-wallet-audit v1.4.0 ruleset — the free MIT GitHub Action that catches Solana wallet anti-patterns in CI: plaintext private keys (base58 OR hex), seed phrases (in comments OR string literals), Anchor.toml wallet leaks, Token2022 transfer-hook abuse, Drift-hack-derived admin bundles, leaked .env files, hardcoded RPC URLs. Free, no payment required.. It is categorised as a Read tool in the CIPHER x402 — Paid Solana & Crypto Tools MCP Server, which means it retrieves data without modifying state.
Register the CIPHER x402 — Paid Solana & Crypto Tools MCP server in PolicyLayer and add a rule for solana_wallet_security_audit_rules: 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 CIPHER x402 — Paid Solana & Crypto Tools. Nothing to install.
solana_wallet_security_audit_rules 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 solana_wallet_security_audit_rules 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 solana_wallet_security_audit_rules. 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.
solana_wallet_security_audit_rules is provided by the CIPHER x402 — Paid Solana & Crypto Tools MCP server (https://cipher-x402-mcp.vercel.app/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 CIPHER x402 — Paid Solana & Crypto Tools 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.