extend_signal_lease
AI agents use extend_signal_lease to create or update resources in Agent Memory Bridge — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Agent Memory Bridge environment.
The tool appears to modify metadata of existing memory signals (extending their lease/lifetime) rather than creating new data or deleting it. This is a reversible write operation. Without a description, confidence is reduced. Severity is medium due to potential impact on memory availability for agent decision-making if leases are improperly extended, but no direct destructive or financial impact.
From the tool's definition Tool name 'extend_signal_lease' suggests modifying the lease duration/expiration of a stored signal, a state-changing operation. The verb 'extend' indicates modification of existing data.
Attacks that exploit this kind of access
extend_signal_lease. It is categorised as a Write tool in the Agent Memory Bridge MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Agent Memory Bridge MCP server in PolicyLayer and add a rule for extend_signal_lease: 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 Agent Memory Bridge. Nothing to install.
extend_signal_lease 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_signal_lease 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_signal_lease. 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_signal_lease is provided by the Agent Memory Bridge MCP server (zzhang82/agent-memory-bridge). 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 →