get_agent_sca_checks
AI agents call get_agent_sca_checks 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 and retrieves SCA (Security Configuration Assessment) check results from Wazuh agents. It has no side effects—it only fetches security assessment data. The severity is medium rather than low because SCA checks may reveal sensitive security configuration details about systems that could be leveraged in attack planning if accessed by an adversarial agent, but the tool itself does not modify or…
From the tool's definition Tool name 'get_agent_sca_checks' indicates a retrieval operation (get_*). The 'sca' component likely refers to Security Configuration Assessment, a Wazuh feature that reports compliance and security posture data.
Attacks that exploit this kind of access
get_agent_sca_checks. 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_agent_sca_checks: 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_agent_sca_checks 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_agent_sca_checks 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_agent_sca_checks. 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_agent_sca_checks 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 →