List events for a device over the past N hours (bounded by default). Auto-resolves device type + site.
AI agents call list_events to retrieve information from API-Central without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries event data with no side effects. It performs a bounded historical lookup without creating, modifying, deleting, or executing operations. The blast radius of misuse is minimal—an attacker gains visibility into network event logs but cannot alter infrastructure or trigger actions.
From the tool's definition Tool name 'list_events' and description 'List events for a device' indicate a retrieval operation. The description specifies it queries past events without modification ('over the past N hours'), and 'Auto-resolves device type + site' describes query…
Attacks that exploit this kind of access
List events for a device over the past N hours (bounded by default). Auto-resolves device type + site. It is categorised as a Read tool in the API-Central MCP Server, which means it retrieves data without modifying state.
Register the API-Central MCP server in PolicyLayer and add a rule for list_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 API-Central. Nothing to install.
list_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 list_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 list_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.
list_events is provided by the API-Central MCP server (secure-ssid/centralmcp). 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 →