Low Risk

recent_transactions

View recent credits and debits (default 20, max 50). Free.

Risk signalsHandles credentials or secrets (api_key)

Part of the Hawaii Conditions MCP Server server.

recent_transactions is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE HAWAII CONDITIONS MCP SERVER →

Free to start. No card required.

AI agents call recent_transactions to retrieve information from Hawaii Conditions MCP Server 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 recent_transactions 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "recent_transactions": {}
  }
}

See the full Hawaii Conditions MCP Server policy for all 20 tools.

Get this rule live on your own Hawaii Conditions MCP Server server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HAWAII CONDITIONS MCP SERVER →

View all 20 tools →

These attack patterns abuse exactly the kind of access recent_transactions gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so recent_transactions only ever does what you allow.

SECURE HAWAII CONDITIONS MCP SERVER →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the recent_transactions tool do? +

View recent credits and debits (default 20, max 50). Free.. It is categorised as a Read tool in the Hawaii Conditions MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recent_transactions? +

Register the Hawaii Conditions MCP Server MCP server in PolicyLayer and add a rule for recent_transactions: 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 Hawaii Conditions MCP Server. Nothing to install.

What risk level is recent_transactions? +

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

Can I rate-limit recent_transactions? +

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

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

recent_transactions is provided by the Hawaii Conditions MCP Server MCP server (https://hawaii-conditions.vercel.app/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Hawaii Conditions MCP Server tool call.

Deterministic rules across all 20 Hawaii Conditions MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.