Add multiple records to a kintone app (max 100 records per request)
AI agents use addRecords 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.
This tool creates new records in a kintone database, which is a write operation that modifies data. It is not destructive since records can be deleted or modified afterward.
From the tool's definition Tool name 'addRecords' and description 'Add multiple records to a kintone app' indicate creation of new data. The capability to add up to 100 records per request demonstrates bulk write capability with reversible effects.
Attacks that exploit this kind of access
Add multiple records to a kintone app (max 100 records per request). 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.
Register the kintone OAuth MCP Server on Cloudflare Workers MCP server in PolicyLayer and add a rule for addRecords: 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.
addRecords 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 addRecords 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 addRecords. 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.
addRecords 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →