Search MCP audit trail for tool call history. Requires manager role.
AI agents call query_audit_log to retrieve information from Maximo Enterprise MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and searches audit trail data without creating, modifying, or deleting records. It is fundamentally a read operation. While audit logs can contain sensitive information (justifying medium severity rather than low), the tool itself performs no destructive, financial, or executable operations.
From the tool's definition Tool name 'query_audit_log' and description 'Search MCP audit trail for tool call history' indicate retrieval and querying of historical log data with no modification or side effects.
Attacks that exploit this kind of access
Search MCP audit trail for tool call history. Requires manager role. It is categorised as a Read tool in the Maximo Enterprise MCP MCP Server, which means it retrieves data without modifying state.
Register the Maximo Enterprise MCP server in PolicyLayer and add a rule for query_audit_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 Maximo Enterprise MCP. Nothing to install.
query_audit_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 query_audit_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 query_audit_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.
query_audit_log is provided by the Maximo Enterprise MCP server (maximo-enterprise-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 →