upsert_lock_rule
Create or update a record lock rule. For invoices, use lock_scope selected_fields with lock_config.locked_field_keys to lock only chosen fields.
This record as markdown: /tools/sankahq-sanka-mcp/upsert-lock-rule.md
What upsert_lock_rule does on Sanka MCP Server
AI agents use upsert_lock_rule to create or update resources in Sanka MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Sanka MCP Server environment.
Why upsert_lock_rule is rated Medium
This tool modifies configuration/metadata by creating or updating lock rules that control field-level access constraints. While it doesn't delete data, it reversibly changes system state and authorization rules. The blast radius is medium: misconfiguration could lock critical fields or overly restrict data access, but changes can be reversed.
From the tool's definition Tool name 'upsert_lock_rule' explicitly indicates create or update operation. Description states 'Create or update a record lock rule' and provides specific use cases (locking fields on invoices).
Attacks that exploit this kind of access
The rule that runs upsert_lock_rule 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 upsert_lock_rule, this is the rule to start with:
upsert_lock_rule stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Sanka MCP Server, apply this rule, and every upsert_lock_rule call is checked against it from then on.
Questions about upsert_lock_rule
Create or update a record lock rule. For invoices, use lock_scope selected_fields with lock_config.locked_field_keys to lock only chosen fields. It is categorised as a Write tool in the Sanka MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Sanka MCP Server MCP server in PolicyLayer and add a rule for upsert_lock_rule: 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.
upsert_lock_rule is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the upsert_lock_rule 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 upsert_lock_rule. 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.
upsert_lock_rule 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.
More on Sanka MCP Server, and thousands of servers like it.
This server
Across the catalogue