add_records · kintone MCP Server (Python3) MCP

WHAT IT DOES

What add_records does on kintone MCP Server (Python3)

AI agents use add_records 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_records needs a policy

This tool creates new records in a kintone application, which is a reversible data modification (Write category). The batch nature (up to 100 records at once) elevates severity to 'high' due to the potential blast radius if an AI agent misuses this to add incorrect or malicious bulk data. It is not Destructive since additions are reversible by deletion, nor Financial/Execute/Read based on its core function.

From the tool's definition Tool name 'add_records' and description 'Add multiple records to a kintone app (max 100 records)' indicate creation of data. The ability to add up to 100 records in a batch operation represents a significant write scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_records Rate-limited

add_records 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_records": {
      "limits": [
        {
          "counter": "add_records_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_records

What does the add_records tool do? +

Add multiple records to a kintone app (max 100 records). 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_records? +

Register the kintone MCP Server (Python3) MCP server in PolicyLayer and add a rule for add_records: 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_records? +

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

Can I rate-limit add_records? +

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

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

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