AI agents call check_config_status 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.
Absence of description lowers confidence to 0.7, but the pattern of read-only operations on a governance/compliance platform and the 'check' verb strongly suggest this retrieves configuration state rather than modifying it. Classified as Read with low severity since configuration status queries have minimal blast radius.
From the tool's definition Tool name 'check_config_status' suggests querying configuration state. No description provided, but naming convention aligns with sibling 'Read' tools (get_accounts, get_entity_by_id, get_spend_report).
Documented attack patterns abuse exactly the kind of access check_config_status 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 check_config_status:
{
"version": "1",
"default": "deny",
"tools": {
"check_config_status": {}
}
}check_config_status 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.
check_config_status. 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 check_config_status: 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.
check_config_status 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 check_config_status 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 check_config_status. 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.
check_config_status 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.