contract-testing_get_audit_log
Retrieve the audit log of events in the workspace. Parameters: - since (string): Only include events at or after this ISO 8601 timestamp - userUuid (string): Filter events by PactFlow user UUID - type (string): Filter events by type (e.g. 'pact_publication') - sort (string): Sort order: '+timesta...
This record as markdown: /tools/smartbear-mcp/contract-testing-get-audit-log.md
What contract-testing_get_audit_log does on SmartBear MCP
AI agents call contract-testing_get_audit_log to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
from | string | — | Start result set from this audit event UUID (keyset pagination) |
sort | string | — | Sort order: '+timestamp' (asc, default) or '-timestamp' (desc) |
type | string | — | Filter events by type (e.g. 'pact_publication') |
since | string | — | Only include events at or after this ISO 8601 timestamp |
pageSize | integer | — | Results per page (max 100) |
userUuid | string | — | Filter events by PactFlow user UUID |
pageNumber | integer | — | Page number |
Parameters from the server's own tool schema.
Why contract-testing_get_audit_log is rated Low
This is a read-only retrieval tool for audit log data. While it accesses potentially sensitive information (workspace events, user activities, webhook changes, secrets references), it does not modify data, execute code, or cause destructive actions.
From the tool's definition Tool description states 'Retrieve the audit log of events in the workspace' with filtering and pagination parameters. No modification, deletion, or execution capabilities mentioned.
Attacks that exploit this kind of access
The rule that runs contract-testing_get_audit_log safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_get_audit_log, this is the rule to start with:
contract-testing_get_audit_log is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_get_audit_log call is checked against it from then on.
Questions about contract-testing_get_audit_log
Retrieve the audit log of events in the workspace. Parameters: - since (string): Only include events at or after this ISO 8601 timestamp - userUuid (string): Filter events by PactFlow user UUID - type (string): Filter events by type (e.g. 'pact_publication') - sort (string): Sort order: '+timestamp' (asc, default) or '-timestamp' (desc) - from (string): Start result set from this audit event UUID (keyset pagination) - pageNumber (number): Page number - pageSize (number): Results per page (max 100) Use Cases: 1. Review recent changes to pacticipants, webhooks, or secrets 2. Investigate who published a specific pact or verification 3. Filter events by user or event type for compliance reporting 4. Track deployment recording activity across environments. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_get_audit_log accepts 7 parameters: from, sort, type, since, pageSize, userUuid, pageNumber. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_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 SmartBear MCP. Nothing to install.
contract-testing_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 contract-testing_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 contract-testing_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.
contract-testing_get_audit_log is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue