複数レコードを一括Upsertします。各要素に重複禁止フィールド（updateKey）と更新内容を指定すると、存在するレコードは更新、存在しないレコードは新規作成されます。最大100件。
AI agents use upsert_records to create or update resources in Kintone MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Kintone MCP Server environment.
Upsert operations create or modify records based on updateKey matching. These are reversible write operations—data can be modified again or deleted by subsequent calls. The blast radius is limited to the records specified in the operation.
From the tool's definition Tool name 'upsert_records' and description stating it performs bulk upsert operations: 'existing records are updated, non-existing records are created' (更新内容を指定すると、存在するレコードは更新、存在しないレコードは新規作成されます).
Documented attack patterns abuse exactly the kind of access upsert_records gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kintone MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for upsert_records:
{
"version": "1",
"default": "deny",
"tools": {
"upsert_records": {
"limits": [
{
"counter": "upsert_records_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upsert_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.
Free to start. No card required.
複数レコードを一括Upsertします。各要素に重複禁止フィールド（updateKey）と更新内容を指定すると、存在するレコードは更新、存在しないレコードは新規作成されます。最大100件。. It is categorised as a Write tool in the Kintone MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Kintone MCP Server MCP server in PolicyLayer and add a rule for upsert_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. Nothing to install.
upsert_records 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_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.
Set action: deny in the PolicyLayer policy for upsert_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.
upsert_records is provided by the Kintone MCP Server MCP server (r3-yamauchi/kintone-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kintone MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
70 Kintone MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.