AI agents use add_thread_comment 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 comment data within an existing thread, which is a write operation. It modifies thread state by appending new content. The severity is medium because while it creates data, the blast radius is limited to adding comments (reversible via delete), not bulk record manipulation or destructive operations. Confidence is high because the name and description clearly indicate a data creation action.
From the tool's definition add_thread_comment - adds a comment to a thread. The description in Japanese translates to 'Adds a comment to a thread', indicating a create/modify operation on thread data.
Documented attack patterns abuse exactly the kind of access add_thread_comment 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_comment:
{
"version": "1",
"default": "deny",
"tools": {
"add_thread_comment": {
"limits": [
{
"counter": "add_thread_comment_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_thread_comment 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_comment: 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_comment 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_comment 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_comment. 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_comment 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.