AI agents call get_cloud_access_role_details 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.
The 'get_' prefix strongly suggests this tool queries and retrieves access role details from the Kion platform without making changes. No modification, deletion, or execution is implied. While the description is empty (lowering confidence slightly), the naming convention and context of similar retrieval tools on the server indicate this is a Read operation with minimal blast radius if misused.
From the tool's definition Tool name 'get_cloud_access_role_details' uses the 'get' prefix, indicating a retrieval operation. Sibling tools like 'get_accounts', 'get_entity_by_id', 'get_label_key_id', 'get_spend_report', and 'get_user_info' all follow the Read pattern of retrieving…
Documented attack patterns abuse exactly the kind of access get_cloud_access_role_details 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_cloud_access_role_details:
{
"version": "1",
"default": "deny",
"tools": {
"get_cloud_access_role_details": {}
}
}get_cloud_access_role_details 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_cloud_access_role_details. 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_cloud_access_role_details: 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_cloud_access_role_details 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_cloud_access_role_details 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_cloud_access_role_details. 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_cloud_access_role_details 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.