AI agents call central_get_events to retrieve information from Central 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 a network management system. While the description is empty, the name and context strongly suggest read-only querying behavior consistent with other 'central_get_*' tools. Event data itself is not sensitive enough to warrant higher severity, though access to network events could reveal operational details.
From the tool's definition Tool name 'central_get_events' indicates retrieval of event data from HPE Aruba Networking Central. Server description confirms it 'enables AI assistants to query' data including 'events'.
Attacks that exploit this kind of access
central_get_events. It is categorised as a Read tool in the Central MCP Server, which means it retrieves data without modifying state.
Register the Central MCP server in PolicyLayer and add a rule for central_get_events: 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 Central. Nothing to install.
central_get_events 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 central_get_events 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 central_get_events. 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.
central_get_events is provided by the Central MCP server (karthikskumar98/central-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 →