Get the $PEPTM token balance and staking information for a PEPTOMA user or Solana wallet. Returns current balance, staked amount, total earned from research contributions, total spent on analyses, current staking tier (free/researcher/pro/lab), and linked Solana address.
AI agents call get_token_balance to retrieve information from Peptoma without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves financial information (token balance, staking details, earnings) but does not move money, execute transactions, or create financial obligations. It is purely informational about account state, similar to checking a bank balance via a read-only API. The blast radius of misuse is minimal: an attacker gains visibility into a user's wallet state but cannot directly perform transfers or trades.
From the tool's definition Tool description uses 'Get' and 'Returns' indicating read-only retrieval of balance and staking information. No modification, deletion, or financial transaction is performed—only querying existing token balance and wallet data.
Attacks that exploit this kind of access
Get the $PEPTM token balance and staking information for a PEPTOMA user or Solana wallet. Returns current balance, staked amount, total earned from research contributions, total spent on analyses, current staking tier (free/researcher/pro/lab), and linked Solana address. It is categorised as a Read tool in the Peptoma MCP Server, which means it retrieves data without modifying state.
Register the Peptoma MCP server in PolicyLayer and add a rule for get_token_balance: 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 Peptoma. Nothing to install.
get_token_balance 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 get_token_balance 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 get_token_balance. 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.
get_token_balance is provided by the Peptoma MCP server (peptoma/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →