kaspa_get_subscription_status

THE RISK

Low Risk

Why kaspa_get_subscription_status needs a policy

This tool retrieves subscription status and address monitoring information without modifying, deleting, or executing any operations. It is a passive information retrieval function, fitting the 'Read' category. The blast radius is minimal since it only exposes existing monitoring/subscription metadata. Severity is low because disclosure of subscription status poses no direct financial risk or operational harm.

From the tool's definition Tool name contains 'get_subscription_status' and description states 'Get current subscription status and monitored addresses' — both indicate a read-only query operation with no side effects.

Documented attack patterns abuse exactly the kind of access kaspa_get_subscription_status gives an agent:

POLICY

How to control kaspa_get_subscription_status

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_get_subscription_status:

policy.json

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

kaspa_get_subscription_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Kaspa MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Kaspa MCP Server tools

Financial kaspa_send_from_wallet Send Kaspa from your wallet (simplified version) Financial kaspa_send_transaction Send a Kaspa transaction Execute kaspa_connect Connect to Kaspa network (mainnet, testnet-10, devnet, simnet) Write kaspa_create_wallet Create or import a Kaspa wallet Write kaspa_generate_mnemonic Generate a new mnemonic phrase for wallet creation Write kaspa_setup_preconfigured_wallet Setup wallet using preconfigured credentials from environment variables (KASPA_WALLET_MNEM Write kaspa_unsubscribe_balance Unsubscribe from balance change notifications Read kaspa_get_balance Get balance for a Kaspa address

All 15 Kaspa MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about kaspa_get_subscription_status

What does the kaspa_get_subscription_status tool do? +

Get current subscription status and monitored addresses. It is categorised as a Read tool in the Kaspa MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on kaspa_get_subscription_status? +

Register the Kaspa MCP Server MCP server in PolicyLayer and add a rule for kaspa_get_subscription_status: 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.

What risk level is kaspa_get_subscription_status? +

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

Can I rate-limit kaspa_get_subscription_status? +

Yes. Add a rate_limit block to the kaspa_get_subscription_status 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 kaspa_get_subscription_status completely? +

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

kaspa_get_subscription_status 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.

Enforce policy on every Kaspa MCP Server tool call.

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.

CHECK YOUR STACK →