Load lock rule options for an object, including fields, operators, lock scopes, and lockable invoice fields.
AI agents call get_lock_rule_options 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.
This tool retrieves and returns information about lock rule configurations and available options for an object. It performs no side effects, makes no modifications to data, and does not execute code or trigger external operations. This is a straightforward data retrieval operation, making it a Read category tool with low severity.
From the tool's definition The tool name 'get_lock_rule_options' and description 'Load lock rule options' indicate retrieval of configuration metadata (fields, operators, lock scopes, lockable invoice fields).
Attacks that exploit this kind of access
Load lock rule options for an object, including fields, operators, lock scopes, and lockable invoice fields. 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 get_lock_rule_options: 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.
get_lock_rule_options 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_rule_options 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_rule_options. 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_rule_options 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 →