Get records from a kintone app
AI agents call get_records 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 or queries data from a kintone application without modifying, deleting, or executing operations on that data. It is a straightforward read operation consistent with the Read category. The potential security risk is low since it only exposes existing data and does not permit destructive or executable actions.
From the tool's definition Tool name 'get_records' and description 'Get records from a kintone app' indicate a retrieval operation with no side effects. The server description explicitly lists 'record CRUD operations' and categorizes this as data retrieval functionality.
Attacks that exploit this kind of access
Get records from a kintone app. 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_records: 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_records 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_records 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_records. 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_records 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 →