// SCAN REPORT

Wise

11 tools. 0 can modify or destroy data without limits.

Read-only server. Low risk, but rate limits prevent runaway API costs.

Last updated:

0 can modify or destroy data
11 read-only
11 tools total
// TOOL MAP
Read (11) Write / Execute (0) Destructive / Financial (0)
// WHAT CAN GO WRONG
✕

Even read-only tools carry cost. An agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up bills.

// RECOMMENDED RULES
Cap read operations
wise_get_account_requirements:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

// ALL 11 WISE TOOLS
READ 11 tools
Read wise_get_account_requirements Read wise_get_balance Read wise_get_exchange_rate Read wise_get_exchange_rate_history Read wise_get_profile Read wise_get_recipient Read wise_get_transfer Read wise_list_balances Read wise_list_profiles Read wise_list_recipients Read wise_list_transfers
// FAQ
Is the Wise MCP server safe to use without restrictions? +

The Wise server is primarily read-only with 11 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Wise MCP server expose? +

11 tools across 1 categories: Read. 11 are read-only. 0 can modify, create, or delete data.

How do I add Intercept to my Wise setup? +

One line change. Instead of running the Wise server directly, prefix it with Intercept: intercept -c wise.yaml -- npx -y @@aiwerk/mcp-server-wise. Download a pre-built policy from policylayer.com/policies/wise and adjust the limits to match your use case.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

GET STARTED →
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.