recent_trades

THE RISK

Low Risk

Why recent_trades needs a policy

This tool retrieves historical trade data and does not modify, execute operations, delete data, or commit financial transactions. While the server enables trading functionality (evidenced by sibling tools like add_order, amend_order, cancel_order), this specific tool is a passive query mechanism.

From the tool's definition Tool name is 'recent_trades' and description states 'Recent trades' with pagination via 'last' field, indicating a retrieval operation with no side effects.

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

POLICY

How to control recent_trades

PolicyLayer is an MCP gateway — it sits between your AI agents and Kraken Pro MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for recent_trades:

policy.json

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

recent_trades 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 Kraken Pro MCP — 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 Kraken Pro MCP tools

Financial cancel_all_orders_after Dead man's switch: set countdown to cancel ALL your orders after timeout_seconds. Financial amend_order Atomic amend in-place (keeps identifiers & queue priority where possible). Financial add_order Place a new Kraken Spot order (REST AddOrder). Destructive cancel_order Cancel a particular open order (or set of orders). Read account_balance Get Account Balance: all cash balances, net of pending withdrawals. Read asset_info Asset metadata. Example assets: 'XBT,ETH,USDT' Read closed_orders closed_orders Read ohlc OHLC candles.

All 17 Kraken Pro MCP 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 recent_trades

What does the recent_trades tool do? +

Recent trades. Use the returned 'last' field as your next since. It is categorised as a Read tool in the Kraken Pro MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on recent_trades? +

Register the Kraken Pro MCP server in PolicyLayer and add a rule for recent_trades: 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 Kraken Pro MCP. Nothing to install.

What risk level is recent_trades? +

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

Can I rate-limit recent_trades? +

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

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

recent_trades is provided by the Kraken Pro MCP server (oilst/kraken-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Kraken Pro MCP tool call.

Start from Kraken Pro MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →