41 tools. 19 can modify or destroy data without limits.
18 destructive tools with no built-in limits. Policy required.
Last updated:
Community server · catalogue entry checked 03/09/2026
Running more than one server? Check your whole stack →
19 of Q402 Mcp's 41 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.
PolicyLayer is an MCP gateway — it sits between your AI agents and Q402 Mcp, and nothing reaches the server without passing your rules. These are the rules we recommend:
{
"q402_bridge_send": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
} Financial tools should be explicitly enabled per use case, not open by default.
{
"q402_clear_delegation": {
"deny_if": [
{
"conditions": [],
"on_deny": "Blocked by default. Requires approval."
}
]
}
} Destructive tools should never be available to autonomous agents without human approval.
{
"q402_request_create": {
"limits": [
{
"counter": "q402_request_create_per_hour",
"window": "hour",
"max": 30,
"scope": "grant"
}
]
}
} Prevents bulk unintended modifications from agents caught in loops.
{
"q402_agent_spend_report": {
"limits": [
{
"counter": "q402_agent_spend_report_per_minute",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
} Controls API costs and prevents retry loops from exhausting upstream rate limits.
Instant setup, no code required.
Other MCP servers with similar tools — same risk classification, starter policies for each.
Yes. The Q402 Mcp server exposes 16 financial tools including q402_bridge_send, q402_escrow_create, q402_escrow_dispute. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.
Yes. The Q402 Mcp server exposes 2 destructive tools including q402_clear_delegation, q402_redstone_trigger_cancel. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.
The Q402 Mcp server has 1 write tools including q402_request_create. Set a rate limit in your policy -- for example, 10 calls per hour prevents an agent from making more than 10 modifications per hour. PolicyLayer enforces this at the gateway, before calls reach Q402 Mcp.
41 tools across 5 categories: Destructive, Execute, Financial, Read, Write. 22 are read-only. 19 can modify, create, or delete data.
Register the Q402 MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.
Deterministic rules across all 41 Q402 Mcp tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Instant setup, no code required.
41 Q402 Mcp tools catalogued and risk-classified — across an index of 46,500+ MCP servers.
These policies come from Q402's registry record.
The record behind this page: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →