Low Risk

cloak_balance

Check available wallet balance

Part of the Cloaked Agent MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

@cloakedagent/sdk Read Risk 2/5

AI agents call cloak_balance to retrieve information from Cloaked Agent without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.

Even though cloak_balance only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.

Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.

cloaked-agent.yaml
tools:
  cloak_balance:
    rules:
      - action: allow

See the full Cloaked Agent policy for all 4 tools.

Tool Name cloak_balance
Category Read
Risk Level Low

Agents calling read-class tools like cloak_balance have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.

What does the cloak_balance tool do? +

Check available wallet balance. It is categorised as a Read tool in the Cloaked Agent MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cloak_balance? +

Add a rule in your Intercept YAML policy under the tools section for cloak_balance. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Cloaked Agent MCP server.

What risk level is cloak_balance? +

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

Can I rate-limit cloak_balance? +

Yes. Add a rate_limit block to the cloak_balance rule in your Intercept 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 cloak_balance completely? +

Set action: deny in the Intercept policy for cloak_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.

What MCP server provides cloak_balance? +

cloak_balance is provided by the Cloaked Agent MCP server (@cloakedagent/sdk). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Cloaked Agent

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.