list_lock_rules

List record lock rules for a Sanka object.

SERVERSanka MCP Server SOURCEsankahq/sanka-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sankahq-sanka-mcp/list-lock-rules.md

WHAT IT DOES

What list_lock_rules does on Sanka MCP Server

AI agents call list_lock_rules to retrieve information from Sanka MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why list_lock_rules is rated Low

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

RECOMMENDED RULE

The rule that runs list_lock_rules safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sanka MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For list_lock_rules, this is the rule to start with:

list_lock_rules Allowed

list_lock_rules is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "list_lock_rules": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every list_lock_rules call is checked against it from then on.

FAQ

Questions about list_lock_rules

What does the list_lock_rules tool do? +

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.

How do I enforce a policy on list_lock_rules? +

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.

What risk level is list_lock_rules? +

list_lock_rules is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit list_lock_rules? +

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.

How do I block list_lock_rules completely? +

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.

What MCP server provides list_lock_rules? +

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.

KEEP EXPLORING

More on Sanka MCP Server, and thousands of servers like it.

This server

All 349 Sanka MCP Server tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →