kintoneレコードのコメントを取得します。limit未指定の場合は内部でページングして全件を取得します。大量データになる場合は limit（例: 10）を指定することを推奨します。
AI agents call get_record_comments to retrieve information from Kintone MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves comments associated with records in a Kintone database. It performs a straightforward data query operation with no capacity to create, modify, delete, or execute external operations. The pagination controls confirm its purpose is controlled data retrieval. Misuse by an AI agent would be limited to exposing sensitive comment content, which is a low-severity information disclosure risk.
From the tool's definition Tool description states 'get_record_comments' retrieves comments from Kintone records. The word 'get' and '取得' (retrieve/fetch) indicate a read-only operation that returns existing data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_record_comments 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 get_record_comments:
{
"version": "1",
"default": "deny",
"tools": {
"get_record_comments": {}
}
}get_record_comments is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
kintoneレコードのコメントを取得します。limit未指定の場合は内部でページングして全件を取得します。大量データになる場合は limit（例: 10）を指定することを推奨します。. It is categorised as a Read tool in the Kintone MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kintone MCP Server MCP server in PolicyLayer and add a rule for get_record_comments: 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.
get_record_comments is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_record_comments 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 get_record_comments. 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.
get_record_comments 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.