📋 Get audit log with optional filters.
AI agents call rbac_get_audit_log to retrieve information from n8n Workflow Builder without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves audit log records for inspection and analysis purposes. It has no side effects—it queries existing data without creating, modifying, or deleting anything. Audit log access is informational and supports compliance/debugging activities. Even if audit logs contain sensitive information, the tool itself only reads and does not change system state.
From the tool's definition Tool name 'rbac_get_audit_log' and description 'Get audit log with optional filters' indicate retrieval of existing audit log data without modification. The 'Get' verb and lack of any mutation language (create, delete, modify) confirm read-only behavior.
Attacks that exploit this kind of access
📋 Get audit log with optional filters. It is categorised as a Read tool in the n8n Workflow Builder MCP Server, which means it retrieves data without modifying state.
Register the n8n Workflow Builder MCP server in PolicyLayer and add a rule for rbac_get_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 n8n Workflow Builder. Nothing to install.
rbac_get_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 rbac_get_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 rbac_get_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.
rbac_get_audit_log is provided by the n8n Workflow Builder MCP server (schimmilab/n8n-workflow-builder). 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 →