Get comments from a kintone record
AI agents call getRecordComments to retrieve information from kintone OAuth MCP Server on Cloudflare Workers without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves comment data from a kintone record. It performs a read-only operation that does not create, modify, delete, or execute any actions. The verb 'Get' and the absence of any language suggesting state changes, deletion, or code execution clearly position this as a Read category tool with low severity risk.
From the tool's definition Tool name 'getRecordComments' and description 'Get comments from a kintone record' indicate retrieval of existing data with no modification or side effects.
Attacks that exploit this kind of access
Get comments from a kintone record. It is categorised as a Read tool in the kintone OAuth MCP Server on Cloudflare Workers MCP Server, which means it retrieves data without modifying state.
Register the kintone OAuth MCP Server on Cloudflare Workers MCP server in PolicyLayer and add a rule for getRecordComments: 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.
getRecordComments 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 getRecordComments 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 getRecordComments. 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.
getRecordComments 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 →