List record lock rules for a Sanka object.
AI agents call list_lock_rules to retrieve information from Sanka MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The verb 'list' denotes a read-only query operation. The function retrieves and returns lock rules configuration for inspection, producing no side effects or data modifications. While the sibling tools include destructive and write operations (activate_*, approve_*, archive_*), this specific tool is clearly a non-destructive information retrieval operation with minimal blast radius if misused.
From the tool's definition Tool name 'list_lock_rules' and description 'List record lock rules for a Sanka object' indicate a retrieval operation that queries existing lock rule configuration data without modification.
Attacks that exploit this kind of access
List record lock rules for a Sanka object. It is categorised as a Read tool in the Sanka MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for list_lock_rules: 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 Sanka MCP Server. Nothing to install.
list_lock_rules 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 list_lock_rules 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 list_lock_rules. 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.
list_lock_rules is provided by the Sanka MCP Server MCP server (sankahq/sanka-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 →