Check lock status and queue for a resource.
AI agents call get_lock_status to retrieve information from Mnehmos Synch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves information about lock status and queue state without creating, modifying, deleting, or executing any operations. It is purely informational and falls squarely into the Read category with minimal risk due to its non-destructive nature.
From the tool's definition Tool name 'get_lock_status' and description 'Check lock status and queue for a resource' indicate a read-only operation that queries the current state of a lock without modifying any data or triggering side effects.
Attacks that exploit this kind of access
Check lock status and queue for a resource. It is categorised as a Read tool in the Mnehmos Synch MCP Server, which means it retrieves data without modifying state.
Register the Mnehmos Synch MCP server in PolicyLayer and add a rule for get_lock_status: 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 Mnehmos Synch. Nothing to install.
get_lock_status 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_lock_status 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_lock_status. 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_lock_status is provided by the Mnehmos Synch MCP server (mnehmos/mnehmos.synch.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 →