AI agents use create_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.
This tool creates new records in a Kintone database application. Record creation is a reversible write operation—records can be deleted or edited afterward. While bulk creation of up to 100 records poses a meaningful blast radius if misused (data pollution, storage consumption, duplicates), it does not irreversibly destroy data (Destructive) nor move money (Financial).
From the tool's definition Tool name 'create_records' and description 'kintoneアプリに複数のレコードを一括作成します（最大100件）' (creates multiple records in a Kintone app in bulk, up to 100) indicates the tool creates/writes data.
Documented attack patterns abuse exactly the kind of access create_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 create_records:
{
"version": "1",
"default": "deny",
"tools": {
"create_records": {
"limits": [
{
"counter": "create_records_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_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.
kintoneアプリに複数のレコードを一括作成します（最大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 create_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.
create_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 create_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 create_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.
create_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.