sf_get_setup_audit_trail

Queries the SetupAuditTrail object to see who made what configuration changes to the org, and when. Covers the last 6 months of setup activity. Returns records with: date, username, section, action, display (human-readable description) section filter examples:

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-get-setup-audit-trail.md

What sf_get_setup_audit_trail does on Salesforce Metadata Mcp

AI agents call sf_get_setup_audit_trail to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why sf_get_setup_audit_trail is rated Low

This tool retrieves and queries historical audit log data from a read-only system object (SetupAuditTrail). It has no side effects, does not modify data, and simply provides visibility into past configuration changes. The data returned is informational metadata about org activity.

From the tool's definition Queries the SetupAuditTrail object to see who made what configuration changes to the org. Returns records with: date, username, section, action, display.

Questions about sf_get_setup_audit_trail

What does the sf_get_setup_audit_trail tool do? +

Queries the SetupAuditTrail object to see who made what configuration changes to the org, and when. Covers the last 6 months of setup activity. Returns records with: date, username, section, action, display (human-readable description) section filter examples:. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sf_get_setup_audit_trail? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_get_setup_audit_trail: 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 Salesforce Metadata Mcp. Nothing to install.

What risk level is sf_get_setup_audit_trail? +

sf_get_setup_audit_trail is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sf_get_setup_audit_trail? +

Yes. Add a rate_limit block to the sf_get_setup_audit_trail 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.

How do I block sf_get_setup_audit_trail completely? +

Set action: deny in the PolicyLayer policy for sf_get_setup_audit_trail. 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.

What MCP server provides sf_get_setup_audit_trail? +

sf_get_setup_audit_trail is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Salesforce Metadata, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Salesforce Metadata's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.