get_index_mapping
AI agents call get_index_mapping 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 'get_' prefix strongly suggests a retrieval operation with no side effects. The lack of description lowers confidence slightly, but the pattern of sibling tools on the Wazuh MCP server (all read operations for monitoring and analysis) supports classification as a Read operation.
From the tool's definition Tool named 'get_index_mapping' with no description provided. Based on naming convention ('get_' prefix) and sibling tools that are predominantly read-only information retrieval functions (get_agent_component_stats, get_agent_daemon_stats, get_agent_hardware,…
Attacks that exploit this kind of access
get_index_mapping. 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_index_mapping: 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_index_mapping 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_index_mapping 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_index_mapping. 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_index_mapping 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 →