Check if the user has permission to uninstall agents.
AI agents call get_check_user_uninstall_permission to retrieve information from Wazuh MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries whether a user possesses uninstall permissions; it performs a read-only check of access control metadata. While the uninstall action itself would be destructive, this tool merely checks permissions and has no side effects. It falls clearly into the Read category as a get/check operation that returns permission information.
From the tool's definition Tool name contains 'get_check' and description states 'Check if the user has permission' — this is a permission query operation that retrieves authorization status without modifying any state.
Attacks that exploit this kind of access
Check if the user has permission to uninstall agents. It is categorised as a Read tool in the Wazuh MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Wazuh MCP Server MCP server in PolicyLayer and add a rule for get_check_user_uninstall_permission: 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 Wazuh MCP Server. Nothing to install.
get_check_user_uninstall_permission 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_check_user_uninstall_permission 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_check_user_uninstall_permission. 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_check_user_uninstall_permission is provided by the Wazuh MCP Server MCP server (rayasatriatama/wazuh-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →