Check if a specific feature is enabled for the account
AI agents call check_feature to retrieve information from cPanel MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to determine feature enablement status. It has no side effects, does not execute code or commands, does not modify data, and does not involve financial transactions. The blast radius of misuse is minimal—an agent could only learn what features are available, which is low-risk information in a hosting context.
From the tool's definition Tool name 'check_feature' and description 'Check if a specific feature is enabled for the account' indicate a query operation that retrieves configuration status without modifying any data or triggering external operations.
Documented attack patterns abuse exactly the kind of access check_feature gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and cPanel MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for check_feature:
{
"version": "1",
"default": "deny",
"tools": {
"check_feature": {}
}
}check_feature 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 if a specific feature is enabled for the account. It is categorised as a Read tool in the cPanel MCP Server MCP Server, which means it retrieves data without modifying state.
Register the cPanel MCP Server MCP server in PolicyLayer and add a rule for check_feature: 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 cPanel MCP Server. Nothing to install.
check_feature 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_feature 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_feature. 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_feature is provided by the cPanel MCP Server MCP server (0xhayd3n/cpanel-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from cPanel 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.
164 cPanel MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.