Extend the duration of an existing LP lock. Only the lock owner can extend. Requires DEPLOYER_PRIVATE_KEY env var.
AI agents use extend_lock to create or update resources in Base Lp Locker — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Base Lp Locker environment.
This tool modifies an existing on-chain LP lock by extending its duration. It is a Write operation as it updates state (lock duration) but does not delete, move funds, or execute arbitrary code. However, severity is high because it uses a private key to sign blockchain transactions, and misuse could extend lock periods unexpectedly, preventing legitimate withdrawal of LP tokens for a longer time than intended.
From the tool's definition Extend the duration of an existing LP lock. Only the lock owner can extend. Requires DEPLOYER_PRIVATE_KEY env var.
Attacks that exploit this kind of access
Extend the duration of an existing LP lock. Only the lock owner can extend. Requires DEPLOYER_PRIVATE_KEY env var. It is categorised as a Write tool in the Base Lp Locker MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Base Lp Locker MCP server in PolicyLayer and add a rule for extend_lock: 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.
extend_lock 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 extend_lock 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 extend_lock. 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.
extend_lock 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 →