updateRecord | PolicyLayer

WHAT IT DOES

What updateRecord does on kintone OAuth MCP Server on Cloudflare Workers

AI agents use updateRecord to create or update resources in kintone OAuth MCP Server on Cloudflare Workers — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your kintone OAuth MCP Server on Cloudflare Workers environment.

WHY IT NEEDS A POLICY

Why updateRecord needs a policy

This tool creates or modifies data reversibly, which is the defining characteristic of the Write category. It updates a record (modifies an existing entity) rather than deleting it (Destructive) or executing arbitrary code (Execute). The severity is medium because unauthorized updates could corrupt or manipulate business data, but the action is reversible via subsequent updates.

From the tool's definition Tool description: 'Update an existing record in a kintone app'. The name 'updateRecord' and description clearly indicate modification of existing data in a reversible manner.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

updateRecord Rate-limited

updateRecord 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": {
    "updateRecord": {
      "limits": [
        {
          "counter": "updaterecord_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 kintone OAuth MCP Server on Cloudflare Workers, so you can run agents against it safely.

FAQ

Questions about updateRecord

What does the updateRecord tool do? +

Update an existing record in a kintone app. It is categorised as a Write tool in the kintone OAuth MCP Server on Cloudflare Workers MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on updateRecord? +

Register the kintone OAuth MCP Server on Cloudflare Workers MCP server in PolicyLayer and add a rule for updateRecord: 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 kintone OAuth MCP Server on Cloudflare Workers. Nothing to install.

What risk level is updateRecord? +

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

Can I rate-limit updateRecord? +

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

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

updateRecord is provided by the kintone OAuth MCP Server on Cloudflare Workers MCP server (r3-yamauchi/kintone-oauth-mcp-server-cfw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.