Get all lock IDs for a given wallet address. Returns an array of lock IDs that can be queried individually with get_lock.
AI agents call get_user_locks to retrieve information from Base Lp Locker without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns lock information for a wallet address without modifying, deleting, or executing any operations. It is purely informational data retrieval, fitting the 'Read' category with low severity since it does not enable misuse with significant blast radius.
From the tool's definition Tool name 'get_user_locks' and description 'Get all lock IDs for a given wallet address. Returns an array of lock IDs' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Get all lock IDs for a given wallet address. Returns an array of lock IDs that can be queried individually with get_lock. It is categorised as a Read tool in the Base Lp Locker MCP Server, which means it retrieves data without modifying state.
Register the Base Lp Locker MCP server in PolicyLayer and add a rule for get_user_locks: 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 Base Lp Locker. Nothing to install.
get_user_locks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_user_locks 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 get_user_locks. 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.
get_user_locks is provided by the Base Lp Locker MCP server (lordbasilaiassistant-sudo/base-lp-locker-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →