New MCP tool for retrieving user audit trails from Harness

[abhishek-singh0710]

This PR adds a new MCP tool for retrieving user audit trails from Harness

Features

• Retrieves the complete audit trail for a specified user within Harness
• Supports filtering by organization, project, and module(s)
• Allows time-bounded queries using start and end time (in milliseconds)
• Includes pagination support for large audit result sets
• Returns detailed audit event information, including resource, action, timestamp, and module

Required Parameters

• user_id: The user ID for whom to retrieve the audit trail

Optional Parameters

• start_time: Start time for audit events (milliseconds since epoch, default: 0)
• end_time: End time for audit events (milliseconds since epoch, default: current time)
• org_id, project_id: Scope filters for organization and project
• Pagination parameters: page, size

Testing

• Verified audit retrieval for a variety of users, organizations, and projects
• Tested filtering by module and time range
• Confirmed pagination returns expected results for large audit sets

[CLAassistant]

All committers have signed the CLA.

[akshay-khole]

its best to standardize routingId, accountIdentifier etc as consts across all clients

[abhishek-singh0710]

Following the other code files, I've kept this separate in the audit file.

[akshay-khole]

what purpose does this filtertype serve ?

[abhishek-singh0710]

That was a field as mentioned in the API Documentation.

[akshay-khole]

Please make sure to match terminology in UI . e.g. Modules is not clear to end user
Indent properly

[abhishek-singh0710]

I have removed that since post-filtering is being done.

[akshay-khole]

what is insertId ?

[abhishek-singh0710]

This entire struct has been removed.

[akshay-khole]

see if math package can solve your requirements

[abhishek-singh0710]

I have used the math package to clamp the values.

[thisrohangupta]

We need to review this