AI agents use add_thread 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.
The tool creates (adds) new thread objects in a Kintone space, which is a Write operation. It modifies the space by adding collaborative content, but the action is reversible (threads can be deleted). Severity is medium because misuse could spam threads or clutter spaces, but the blast radius is limited to the affected space and threads can be cleaned up.
From the tool's definition Tool name 'add_thread' and description '스페이스에 스레드를 추가합니다' (adds a thread to a space) indicates creation of new collaboration/discussion content. This is reversible and creates new data without destructive or financial implications.
Documented attack patterns abuse exactly the kind of access add_thread 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 add_thread:
{
"version": "1",
"default": "deny",
"tools": {
"add_thread": {
"limits": [
{
"counter": "add_thread_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_thread 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.
スペースにスレッドを追加します. 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 add_thread: 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.
add_thread 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 add_thread 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 add_thread. 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.
add_thread 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.