AI agents use upload_file 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.
Uploading a file creates new data in the Kintone app and is reversible (files can be deleted). This is a Write operation rather than Read (no data retrieval), Execute (no arbitrary code execution), Destructive (not irreversible), or Financial (no monetary impact).
From the tool's definition Tool name 'upload_file' and description 'kintoneアプリにファイルをアップロードします' (uploads a file to a Kintone app) indicates file creation/addition to a system. Sibling tools include record creation and comment addition, establishing this as part of a Write-capable suite.
Documented attack patterns abuse exactly the kind of access upload_file 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 upload_file:
{
"version": "1",
"default": "deny",
"tools": {
"upload_file": {
"limits": [
{
"counter": "upload_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}upload_file 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アプリにファイルをアップロードします. 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 upload_file: 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.
upload_file 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 upload_file 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 upload_file. 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.
upload_file 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.