Get comments for a record
AI agents call get_comments to retrieve information from kintone MCP Server (Python3) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves comment data associated with a kintone record. It performs a query/fetch operation that has no side effects, does not modify data, execute commands, or affect other systems. The primary risk is unauthorized information disclosure (reading comments a user shouldn't access), which is mitigated by underlying authentication controls and is inherent to any read operation.
From the tool's definition Tool description states 'Get comments for a record' - a retrieval operation with no modification or execution of external operations.
Attacks that exploit this kind of access
Get comments for a record. It is categorised as a Read tool in the kintone MCP Server (Python3) MCP Server, which means it retrieves data without modifying state.
Register the kintone MCP Server (Python3) MCP server in PolicyLayer and add a rule for get_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 (Python3). Nothing to install.
get_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_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_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_comments is provided by the kintone MCP Server (Python3) MCP server (r3-yamauchi/kintone-mcp-server-python3). 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 →