kintone_update_record · Mcp Kintone Lite MCP: Risk & Policy

WHAT IT DOES

What kintone_update_record does on Mcp Kintone Lite

AI agents use kintone_update_record to create or update resources in Mcp Kintone Lite — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Kintone Lite environment.

WHY IT NEEDS A POLICY

Why kintone_update_record needs a policy

This tool modifies existing data in Kintone but does not delete or permanently destroy information. Updates are reversible through version history/revision control, placing it in the Write category rather than Destructive.

From the tool's definition Tool name 'kintone_update_record' and description 'Update an existing record in a Kintone app' indicate modification of data. The mention of 'revision control' suggests the changes are tracked and reversible, distinguishing it from destructive operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

kintone_update_record Rate-limited

kintone_update_record 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "kintone_update_record": {
      "limits": [
        {
          "counter": "kintone_update_record_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Mcp Kintone Lite, so you can run agents against it safely.

FAQ

Questions about kintone_update_record

What does the kintone_update_record tool do? +

Update an existing record in a Kintone app with revision control. ⚠️ Use. It is categorised as a Write tool in the Mcp Kintone Lite MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on kintone_update_record? +

Register the Mcp Kintone Lite MCP server in PolicyLayer and add a rule for kintone_update_record: 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 Mcp Kintone Lite. Nothing to install.

What risk level is kintone_update_record? +

kintone_update_record is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit kintone_update_record? +

Yes. Add a rate_limit block to the kintone_update_record 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 kintone_update_record completely? +

Set action: deny in the PolicyLayer policy for kintone_update_record. 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 kintone_update_record? +

kintone_update_record is provided by the Mcp Kintone Lite MCP server (luvl/mcp-kintone-lite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.