AI agents call resource_check_lock to retrieve information from Mementos without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries the state of locks on a resource without creating, modifying, or deleting anything. It has no side effects and returns informational data only. It falls squarely into the Read category with low severity since checking locks poses minimal risk—the worst outcome is obtaining stale or incorrect lock information, which does not compromise data integrity or enable harmful actions by an AI agent.
From the tool's definition Tool name 'resource_check_lock' and description 'Check active locks on a resource' indicate a read-only query operation that retrieves lock status without modifying state.
Attacks that exploit this kind of access
Check active locks on a resource. It is categorised as a Read tool in the Mementos MCP Server, which means it retrieves data without modifying state.
Register the Mementos MCP server in PolicyLayer and add a rule for resource_check_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 Mementos. Nothing to install.
resource_check_lock 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 resource_check_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 resource_check_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.
resource_check_lock is provided by the Mementos MCP server (@hasna/mementos). 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 →