// SCAN REPORT

Zetrix

55 tools. 20 can modify or destroy data without limits.

20 write tools that can modify data. Rate limits recommended.

Last updated: 6 May 2026

20 can modify or destroy data

35 read-only

55 tools total

// TOOL MAP

Read (35) Write / Execute (20) Destructive / Financial (0)

// WHAT CAN GO WRONG

Write operations (zetrix_contract_generate_advanced, zetrix_contract_init_dev_environment, zetrix_create_keypair) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (zetrix_sdk_invoke_contract, zetrix_sdk_invoke_contract_by_asset, zetrix_sdk_upgrade_contract) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

// RECOMMENDED RULES

Rate limit write operations

zetrix_contract_generate_advanced:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations

zetrix_call_contract:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 55 ZETRIX TOOLS

EXECUTE 3 tools

Execute zetrix_sdk_invoke_contract Execute zetrix_sdk_invoke_contract_by_asset Execute zetrix_sdk_upgrade_contract

WRITE 17 tools

Write zetrix_contract_generate_advanced Write zetrix_contract_init_dev_environment Write zetrix_create_keypair Write zetrix_crypto_generate_keypair Write zetrix_sdk_activate_account Write zetrix_sdk_create_account Write zetrix_sdk_create_contract Write zetrix_sdk_create_log Write zetrix_sdk_issue_asset Write zetrix_sdk_send_asset Write zetrix_sdk_send_gas Write zetrix_sdk_set_metadata Write zetrix_sdk_set_privilege Write zetrix_submit_transaction Write zetrix_ws_connect Write zetrix_ws_disconnect Write zetrix_ws_submit_transaction

READ 35 tools

Read zetrix_call_contract Read zetrix_check_health Read zetrix_contract_get_chain_functions Read zetrix_contract_get_structure_guide Read zetrix_contract_get_testing_guide Read zetrix_contract_get_token_standard Read zetrix_contract_get_utils_functions Read zetrix_crypto_decrypt_key Read zetrix_crypto_encrypt_key Read zetrix_crypto_get_address Read zetrix_crypto_get_public_key Read zetrix_crypto_sign Read zetrix_crypto_validate_key Read zetrix_crypto_verify Read zetrix_get_account Read zetrix_get_account_assets Read zetrix_get_account_base Read zetrix_get_account_metadata Read zetrix_get_balance Read zetrix_get_block Read zetrix_get_latest_block Read zetrix_get_ledger Read zetrix_get_transaction Read zetrix_get_transaction_blob Read zetrix_get_transaction_cache Read zetrix_get_transaction_history Read zetrix_multi_query Read zetrix_sdk_call_contract Read zetrix_sdk_get_balance Read zetrix_sdk_get_nonce Read zetrix_sdk_is_activated Read zetrix_test_transaction Read zetrix_version Read zetrix_ws_status Read zetrix_ws_subscribe_tx

// FAQ

How do I prevent bulk modifications through Zetrix? +

The Zetrix server has 17 write tools including zetrix_contract_generate_advanced, zetrix_contract_init_dev_environment, zetrix_create_keypair. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Zetrix MCP server expose? +

55 tools across 3 categories: Execute, Read, Write. 35 are read-only. 20 can modify, create, or delete data.

How do I add Intercept to my Zetrix setup? +

One line change. Instead of running the Zetrix server directly, prefix it with Intercept: intercept -c zetrix.yaml -- npx -y @zetrix-mcp-server. Download a pre-built policy from policylayer.com/policies/zetrix and adjust the limits to match your use case.

// RELATED SERVERS

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

Zetrix

Other MCP servers with similar tools.

Let agents act without letting them run wild.