Subscribe to balance changes for wallet addresses
AI agents call kaspa_subscribe_balance to retrieve information from Kaspa MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool sets up a subscription to monitor balance changes, which is a read/observe operation. It does not move funds, modify data, or execute commands. The subscription itself is a read-like operation that listens for events. Severity is low as subscribing to balance updates has minimal blast radius, though it could be used to monitor wallet activity.
From the tool's definition Subscribe to balance changes for wallet addresses
Documented attack patterns abuse exactly the kind of access kaspa_subscribe_balance gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kaspa MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for kaspa_subscribe_balance:
{
"version": "1",
"default": "deny",
"tools": {
"kaspa_subscribe_balance": {}
}
} kaspa_subscribe_balance 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.
Subscribe to balance changes for wallet addresses. It is categorised as a Read tool in the Kaspa MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_subscribe_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 Kaspa MCP Server. Nothing to install.
kaspa_subscribe_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 kaspa_subscribe_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 kaspa_subscribe_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.
kaspa_subscribe_balance is provided by the Kaspa MCP Server MCP server (pichukov/kaspa-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kaspa MCP Server, 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.
15 Kaspa MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.