List audit log events for a Portkey workspace or organization. Returns paginated action-level records with actor, resource, metadata, and timestamps for compliance or incident review; use this instead of analytics when you need individual events, not aggregates. Enterprise-gated. Returns 403 on n...
AI agents call list_audit_logs to retrieve information from Portkey Admin without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
action | string | — | Filter by action type (e.g., 'create', 'update', 'delete', 'login') |
actor_id | string | — | Filter by the user ID who performed the action |
end_time | string | — | End of time range filter (ISO 8601 format, e.g., '2024-01-31T23:59:59Z') |
page_size | number | — | Number of results per page (max 100) |
start_time | string | — | Start of time range filter (ISO 8601 format, e.g., '2024-01-01T00:00:00Z') |
resource_id | string | — | Filter by specific resource ID |
current_page | number | — | Page number for pagination (starts at 1) |
workspace_id | string | — | Filter audit logs by workspace ID |
resource_type | string | — | Filter by resource type (e.g., 'user', 'workspace', 'config', 'virtual_key') |
Parameters from the server's own tool schema.
Even though list_audit_logs only reads data, uncontrolled read access leaks sensitive information and racks up API costs — an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
List audit log events for a Portkey workspace or organization. Returns paginated action-level records with actor, resource, metadata, and timestamps for compliance or incident review; use this instead of analytics when you need individual events, not aggregates. Enterprise-gated. Returns 403 on non-Enterprise Portkey plans. It is categorised as a Read tool in the Portkey Admin MCP Server, which means it retrieves data without modifying state.
list_audit_logs accepts 9 parameters: action, actor_id, end_time, page_size, start_time, resource_id, current_page, workspace_id, resource_type. The full parameter table on this page comes from the server's own tool schema.
Register the Portkey Admin MCP server in PolicyLayer and add a rule for list_audit_logs: 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 Portkey Admin. Nothing to install.
list_audit_logs 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_audit_logs 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_audit_logs. 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_audit_logs is provided by the Portkey Admin MCP server (CodesWhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.