Finance District

16 tools. 7 can modify or destroy data without limits.

4 destructive tools with no built-in limits. Policy required.

Last updated:

7 can modify or destroy data
9 read-only
16 tools total
Read (9) Write / Execute (3) Destructive / Financial (4)

Financial operations (depositForYield, transferTokens, withdrawFromYield) can move real money. An agent caught in a loop could drain accounts before anyone notices.

Destructive tools (onboardingAssistant) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (reportIssue, resolveNameService) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (swapTokens) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Finance District. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @finance-district/agent-wallet
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Block financial tools by default
depositForYield:
  rules:
    - action: deny

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations
onboardingAssistant:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
reportIssue:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
authorizePayment:
  rules:
    - rate_limit: 60/minute

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

Can an AI agent move money through the Finance District MCP server? +

Yes. The Finance District server exposes 3 financial tools including depositForYield, transferTokens, withdrawFromYield. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. Intercept lets you block financial tools by default or set per-tool rate limits.

Can an AI agent delete data through the Finance District MCP server? +

Yes. The Finance District server exposes 1 destructive tools including onboardingAssistant. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Finance District? +

The Finance District server has 2 write tools including reportIssue, resolveNameService. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Finance District MCP server expose? +

16 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 9 are read-only. 7 can modify, create, or delete data.

How do I add Intercept to my Finance District setup? +

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

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Scans your MCP config. Opens a web UI. Protected tool calls in 30 seconds.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.