get_agents_ciscat
AI agents call get_agents_ciscat 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.
The naming convention strongly suggests this tool retrieves CIS-CAT assessment data for Wazuh agents, which is a read operation that queries security compliance information. No side effects or data modification are implied.
From the tool's definition Tool name 'get_agents_ciscat' follows the 'get_' prefix pattern consistent with sibling read-only tools like 'get_agent_component_stats', 'get_agent_daemon_stats', 'get_agent_hardware', 'get_agent_hotfixes', 'get_agent_key', and 'get_agent_netaddr'.
Attacks that exploit this kind of access
get_agents_ciscat. 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_agents_ciscat: 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_agents_ciscat 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_agents_ciscat 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_agents_ciscat. 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_agents_ciscat 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 →