AI agents call BalanceChange to retrieve information from Phalcon without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Given the name 'BalanceChange' and the context of sibling tools (GetChainIdByName, TransactionOverview, Trace) that appear to be blockchain/chain inspection utilities, this tool likely retrieves or queries balance change data without modifying state. The empty description reduces confidence, but the naming pattern and peer tools suggest a read operation.
From the tool's definition Tool name 'BalanceChange' suggests retrieval or tracking of balance modifications. Description is empty, limiting definitive classification.
Documented attack patterns abuse exactly the kind of access BalanceChange gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Phalcon, and nothing reaches the server without passing your rules. This is the rule we recommend for BalanceChange:
{
"version": "1",
"default": "deny",
"tools": {
"BalanceChange": {}
}
}BalanceChange is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
BalanceChange. It is categorised as a Read tool in the Phalcon MCP Server, which means it retrieves data without modifying state.
Register the Phalcon MCP server in PolicyLayer and add a rule for BalanceChange: 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 Phalcon. Nothing to install.
BalanceChange 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 BalanceChange 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 BalanceChange. 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.
BalanceChange is provided by the Phalcon MCP server (mark3labs/phalcon-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Phalcon, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Phalcon tools catalogued and risk-classified — across an index of 43,000+ MCP servers.