add_record · kintone MCP Server (Python3) MCP: Risk & Policy

WHAT IT DOES

What add_record does on kintone MCP Server (Python3)

AI agents use add_record to create or update resources in kintone MCP Server (Python3) — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your kintone MCP Server (Python3) environment.

WHY IT NEEDS A POLICY

Why add_record needs a policy

This tool creates new records in a kintone database, which is a reversible Write operation. It modifies data state but does not delete, execute code, move money, or cause irreversible changes.

From the tool's definition Tool name 'add_record' and description 'Add a single record to a kintone app' explicitly indicate record creation. The server description confirms this is a CRUD tool for 'record...operations' that creates data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_record Rate-limited

add_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": {
    "add_record": {
      "limits": [
        {
          "counter": "add_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 kintone MCP Server (Python3), so you can run agents against it safely.

FAQ

Questions about add_record

What does the add_record tool do? +

Add a single record to a kintone app. It is categorised as a Write tool in the kintone MCP Server (Python3) MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on add_record? +

Register the kintone MCP Server (Python3) MCP server in PolicyLayer and add a rule for add_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 kintone MCP Server (Python3). Nothing to install.

What risk level is add_record? +

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

Can I rate-limit add_record? +

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

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

add_record is provided by the kintone MCP Server (Python3) MCP server (r3-yamauchi/kintone-mcp-server-python3). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

add_record is one line of kintone MCP Server (Python3)'s registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →