Verify a pinned tool list (7Maps)
verify_lockUse this to check that an MCP server's tools are still the ones a person approved, like a lockfile: pass the lock you saved at approval (tool name to hash, as returned by watch or tool_card) and get, per tool, unchanged, changed (with any rise in risk), removed or new. Catches rug pulls, where a tool changes after approval, which MCP clients do not re-ask about. Which to use: verify_lock against your saved lock; watch for one server since a date; changes_since for many servers. Paid per server (see list_paid_tools). Reads the map only.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"server": "<server>",
"lock": "<lock>"
},
"name": "verify_lock"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| lock | Yes | Tool name to hash, saved at approval | |
| server | Yes | The server URL or its official registry name | |
| last_trip | No | Optional: how your previous call to a server 7Maps named went | |
| license_key | No | 7IT plan license key; else pay per call (x402) |