AI agents call get_entity_by_id 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 conventionally signals data retrieval without modification or side effects. Without a description, confidence is reduced, but context from sibling tools on the same server (which are all read operations for querying governance, compliance, and cost management data) supports classification as Read. No evidence of destructive, financial, or execute-level capabilities.
From the tool's definition Tool name 'get_entity_by_id' indicates a retrieval operation. The description is empty, but the naming convention (get_*) and sibling tools like 'get_accounts', 'get_spend_report', and 'get_user_info' all suggest read-only query patterns within the Kion…
Documented attack patterns abuse exactly the kind of access get_entity_by_id 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_entity_by_id:
{
"version": "1",
"default": "deny",
"tools": {
"get_entity_by_id": {}
}
}get_entity_by_id 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_entity_by_id. 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_entity_by_id: 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_entity_by_id 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_entity_by_id 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_entity_by_id. 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_entity_by_id 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.