AI agents call get_kintone_username 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 queries and returns a username value without creating, modifying, deleting, or executing any operations. It is purely informational retrieval, fitting the Read category. Severity is low because while usernames can be sensitive, this appears to be retrieving the identity of the already-authenticated connection (likely the current user), not exposing arbitrary credentials.
From the tool's definition Tool name 'get_kintone_username' and description 'retrieves the username used for connection to Kintone' indicate a retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_kintone_username 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_kintone_username:
{
"version": "1",
"default": "deny",
"tools": {
"get_kintone_username": {}
}
}get_kintone_username 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_kintone_username: 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_kintone_username 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_kintone_username 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_kintone_username. 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_kintone_username 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.