AI agents call get_user_info to retrieve information from Kion MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves user information from the Kion platform with no apparent side effects or data modification. It follows the 'get_' pattern typical of Read operations. Severity is medium rather than low because user information in a cloud governance platform may include sensitive identity, access, or billing details that could be misused if exposed to an AI agent without proper guardrails.
From the tool's definition Tool name 'get_user_info' indicates a retrieval operation. Description is empty, limiting direct evidence. However, the prefix 'get_' combined with 'user_info' strongly suggests querying user data without modification.
Documented attack patterns abuse exactly the kind of access get_user_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Kion MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_user_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_info": {}
}
}get_user_info 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.
get_user_info. It is categorised as a Read tool in the Kion MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Kion MCP Server MCP server in PolicyLayer and add a rule for get_user_info: 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 Kion MCP Server. Nothing to install.
get_user_info 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_user_info 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_user_info. 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_user_info is provided by the Kion MCP Server MCP server (kionsoftware/kion-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Kion 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.
9 Kion MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.