zetrix_get_account_metadata

// WHEN AI AGENTS USE THIS TOOL

AI agents call zetrix_get_account_metadata to retrieve information from Zetrix 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.

// WHY ENFORCE A POLICY ON ZETRIX_GET_ACCOUNT_METADATA

Even though zetrix_get_account_metadata 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.

// RECOMMENDED POLICY

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

zetrix.yaml

tools:
  zetrix_get_account_metadata:
    rules:
      - action: allow

See the full Zetrix policy for all 55 tools.

// DETAILS

Tool Name zetrix_get_account_metadata

Category Read

MCP Server Zetrix MCP Server

Risk Level Low

// MORE ZETRIX TOOLS

Execute zetrix_sdk_invoke_contract Execute zetrix_sdk_invoke_contract_by_asset Execute zetrix_sdk_upgrade_contract 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

View all 55 tools →

// WHAT CAN GO WRONG

Agents calling read-class tools like zetrix_get_account_metadata have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER READ TOOLS ACROSS MCP SERVERS

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

Firecrawl Web Scraping Server firecrawl_check_crawl_status Firecrawl Web Scraping Server firecrawl_crawl Firecrawl Web Scraping Server firecrawl_deep_research Firecrawl Web Scraping Server firecrawl_extract Firecrawl Web Scraping Server firecrawl_map Firecrawl Web Scraping Server firecrawl_scrape

// RELATED READING

// FAQ

What does the zetrix_get_account_metadata tool do? +

Get metadata associated with an account. It is categorised as a Read tool in the Zetrix MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on zetrix_get_account_metadata? +

Add a rule in your Intercept YAML policy under the tools section for zetrix_get_account_metadata. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Zetrix MCP server.

What risk level is zetrix_get_account_metadata? +

zetrix_get_account_metadata is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit zetrix_get_account_metadata? +

Yes. Add a rate_limit block to the zetrix_get_account_metadata 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.

How do I block zetrix_get_account_metadata completely? +

Set action: deny in the Intercept policy for zetrix_get_account_metadata. 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.

What MCP server provides zetrix_get_account_metadata? +

zetrix_get_account_metadata is provided by the Zetrix MCP server (zetrix-mcp-server). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.