# menese_balance

Get your native token balance on a specific blockchain.

Agent View of the PolicyLayer registry record for `menese_balance`. HTML page: https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-balance

## Facts

- Tool: `menese_balance`
- Server: Mcp Menesesdk (`aboodtt404/mcp-menese-sdk`) — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk.md
- Homepage: https://github.com/Aboodtt404/mcp-menese-sdk
- Risk category: Read (Low risk)
- Registry record: grade D, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "menese_balance",
    "arguments": {}
  }
}
```

## Why menese_balance is rated Low

This tool retrieves account balance information from a blockchain. It performs a read-only query with no ability to modify state, execute transactions, or affect financial positions. While it operates in a DeFi context, the tool itself only fetches data. Severity is low because misuse (e.g., querying balances repeatedly) poses minimal risk compared to tools that can transfer funds or execute transactions.

From the tool's own definition: "Tool name 'menese_balance' and description 'Get your native token balance on a specific blockchain' indicate a query operation that retrieves data without modification or side effects."

## Use case

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

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Mcp Menesesdk:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "menese_balance": {}
  }
}
```

## Other tools on Mcp Menesesdk (10)

- `menese_jobs` — Execute — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-jobs.md
- `menese_lend` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-lend.md
- `menese_send` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-send.md
- `menese_stake` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-stake.md
- `menese_swap` — Financial — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-swap.md
- `menese_portfolio` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-portfolio.md
- `menese_prices` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-prices.md
- `menese_quote` — Read — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-quote.md
- `menese_setup` — Write — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-setup.md
- `menese_strategy` — Write — https://policylayer.com/tools/aboodtt404-mcp-menese-sdk/menese-strategy.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=aboodtt404-mcp-menese-sdk · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/aboodtt404-mcp-menese-sdk