sf_get_field_history
Queries the {Object}History object to retrieve a field-level change history for a specific record. Shows what changed, when, the old and new values, and who made the change. Returns records with: date, field, oldValue, newValue, changedBy objectApiName: the SObject with history tracking enabled, ...
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-get-field-history.md
What sf_get_field_history does on Salesforce Metadata Mcp
AI agents call sf_get_field_history 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_field_history is rated Low
This tool retrieves and queries historical audit trail data from Salesforce without modifying, deleting, or executing operations. It is clearly a Read operation. Severity is medium (not low) because unauthorized access to field change history could expose sensitive business information, system changes, and user actions, presenting a moderate risk if an AI agent accesses records it shouldn't inspect.
From the tool's definition Tool "queries" a history object and "retrieves" field-level change data with read-only fields (date, field, oldValue, newValue, changedBy). No modification, deletion, or execution capability described.
Attacks that exploit this kind of access
The rule that runs sf_get_field_history safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_get_field_history, this is the rule to start with:
sf_get_field_history 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 Salesforce Metadata Mcp, apply this rule, and every sf_get_field_history call is checked against it from then on.
Questions about sf_get_field_history
Queries the {Object}History object to retrieve a field-level change history for a specific record. Shows what changed, when, the old and new values, and who made the change. Returns records with: date, field, oldValue, newValue, changedBy objectApiName: the SObject with history tracking enabled, e.g. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_get_field_history: 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.
sf_get_field_history 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 sf_get_field_history 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 sf_get_field_history. 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.
sf_get_field_history 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.
This server
Across the catalogue