get_account_info

Get comprehensive account information including type (EOA or contract),

SERVERTempo SOURCEarome3/tempo-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/arome3-tempo-mcp/get-account-info.md

WHAT IT DOES

What get_account_info does on Tempo

AI agents call get_account_info to retrieve information from Tempo without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why get_account_info is rated Low

This tool retrieves account metadata (type, presumably balance, status, etc.) without causing state changes, side effects, or executing transactions. Despite being on a financial blockchain server, the tool itself only reads data.

From the tool's definition Tool name is 'get_account_info' and description states 'Get comprehensive account information' — a retrieval operation with no modification or execution of code/transactions.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_account_info safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Tempo, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_account_info, this is the rule to start with:

get_account_info Allowed

get_account_info is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_account_info": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Tempo, apply this rule, and every get_account_info call is checked against it from then on.

FAQ

Questions about get_account_info

What does the get_account_info tool do? +

Get comprehensive account information including type (EOA or contract),. It is categorised as a Read tool in the Tempo MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_account_info? +

Register the Tempo MCP server in PolicyLayer and add a rule for get_account_info: 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 Tempo. Nothing to install.

What risk level is get_account_info? +

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

Can I rate-limit get_account_info? +

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

How do I block get_account_info completely? +

Set action: deny in the PolicyLayer policy for get_account_info. 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 get_account_info? +

get_account_info is provided by the Tempo MCP server (arome3/tempo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Tempo, and thousands of servers like it.

This server

All 61 Tempo tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →