AI agents call get_per_record_notifications 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 only fetches/retrieves notification configuration data for individual records. It does not modify, delete, execute, or create anything. It is a pure read operation with minimal security impact, as notification settings are typically non-sensitive metadata. Low severity because misuse would only expose configuration details without operational consequences.
From the tool's definition Tool name 'get_per_record_notifications' and description 'kintoneアプリのレコード単位の通知設定を取得します' (retrieves notification settings per record in Kintone apps) indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_per_record_notifications 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_per_record_notifications:
{
"version": "1",
"default": "deny",
"tools": {
"get_per_record_notifications": {}
}
}get_per_record_notifications 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アプリのレコード単位の通知設定を取得します. 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_per_record_notifications: 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_per_record_notifications 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_per_record_notifications 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_per_record_notifications. 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_per_record_notifications 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.