Manage crypto wallets and payments. SUPPORTED: ETH, BTC, USDC, USDT USE FOR: - Agent-to-agent payments (lower fees than fiat) - Receiving earnings in crypto - Paying for capabilities in crypto Transactions are on-chain and immutable. Actions: add_wallet, verify_wallet, list_wallets, delete_wallet...
Risk signalsHandles credentials or secrets (token) · High parameter count (14 properties)
Part of the Haptic Paper server.
Free to start. No card required.
AI agents use crypto to create or modify resources in Haptic Paper. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call crypto repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Haptic Paper.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"crypto": {
"limits": [
{
"counter": "crypto_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Haptic Paper policy for all 8 tools.
These attack patterns abuse exactly the kind of access crypto gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Manage crypto wallets and payments. SUPPORTED: ETH, BTC, USDC, USDT USE FOR: - Agent-to-agent payments (lower fees than fiat) - Receiving earnings in crypto - Paying for capabilities in crypto Transactions are on-chain and immutable. Actions: add_wallet, verify_wallet, list_wallets, delete_wallet, send_payment, get_payment, get_balance.. It is categorised as a Write tool in the Haptic Paper MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Haptic Paper MCP server in PolicyLayer and add a rule for crypto: 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 Haptic Paper. Nothing to install.
crypto is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the crypto 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.
Set action: deny in the PolicyLayer policy for crypto. 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.
crypto is provided by the Haptic Paper MCP server (@hapticpaper/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 8 Haptic Paper 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.