Get event logs.
AI agents call get_event_logs to retrieve information from HPE Aruba Networking Central MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves event logs from the HPE Aruba Networking Central system. Retrieval of logs is a read-only operation that does not create, modify, delete, execute code, or commit financial obligations. While event logs may contain sensitive information, the tool itself performs no destructive or system-altering actions.
From the tool's definition Tool name 'get_event_logs' and description 'Get event logs' indicate a retrieval operation with no modification or side effects. The verb 'Get' is explicitly a query/read operation.
Attacks that exploit this kind of access
Get event logs. It is categorised as a Read tool in the HPE Aruba Networking Central MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HPE Aruba Networking Central MCP Server MCP server in PolicyLayer and add a rule for get_event_logs: 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 HPE Aruba Networking Central MCP Server. Nothing to install.
get_event_logs 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_event_logs 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_event_logs. 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_event_logs is provided by the HPE Aruba Networking Central MCP Server MCP server (the-otner/aruba-mcp). 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 →