AI agents call get_event_log to retrieve information from Cimc without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays existing event log data from the CIMC without creating, modifying, deleting, or executing any operations. It is purely informational and read-only, making it a Read category tool with low severity since unauthorized access to event logs poses minimal direct risk compared to tools that control hardware power states or modify BIOS settings.
From the tool's definition Tool name is 'get_event_log' and description states 'Get system event log (SEL) entries' and 'Shows hardware events, errors, and status changes.' The verb 'Get' and 'Shows' indicate retrieval/query operations with no modification of data.
Attacks that exploit this kind of access
Get system event log (SEL) entries from the CIMC. Shows hardware events, errors, and status changes. It is categorised as a Read tool in the Cimc MCP Server, which means it retrieves data without modifying state.
Register the Cimc MCP server in PolicyLayer and add a rule for get_event_log: 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 Cimc. Nothing to install.
get_event_log 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_log 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_log. 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_log is provided by the Cimc MCP server (schwarztim/cimc-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 →