25 tools. 6 can modify or destroy data without limits.
3 destructive tools with no built-in limits. Policy required.
Last updated:
Financial operations (transfer_starknet_eth, transfer_starknet_strk, transfer_starknet_token) can move real money. An agent caught in a loop could drain accounts before anyone notices.
Write operations (resolve_starknet_address, resolve_starknet_name) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.
Execute tools (execute_starknet_contract) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.
Intercept sits between your agent and Starknet MCP Server. 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 @mcpdotdirect/starknet-mcp-server transfer_starknet_eth:
rules:
- action: deny Financial tools should be explicitly enabled per use case, not open by default.
resolve_starknet_address:
rules:
- rate_limit: 30/hour Prevents bulk unintended modifications from agents caught in loops.
call_starknet_contract:
rules:
- rate_limit: 60/minute Controls API costs and prevents retry loops from exhausting upstream rate limits.
Yes. The Starknet MCP Server server exposes 3 financial tools including transfer_starknet_eth, transfer_starknet_strk, transfer_starknet_token. 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.
The Starknet MCP Server server has 2 write tools including resolve_starknet_address, resolve_starknet_name. 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.
25 tools across 4 categories: Execute, Financial, Read, Write. 19 are read-only. 6 can modify, create, or delete data.
One line change. Instead of running the Starknet MCP Server server directly, prefix it with Intercept: intercept -c mcpdotdirect-starknet-mcp-server.yaml -- npx -y @mcpdotdirect/starknet-mcp-server. Download a pre-built policy from policylayer.com/policies/mcpdotdirect-starknet-mcp-server and adjust the limits to match your use case.
Starter policies available for each. Same risk classification, same one-command setup.
Set budgets, approvals, and hard limits across MCP servers.
npx -y @policylayer/intercept init