sf_search_records

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-search-records.md

WHAT IT DOES

What sf_search_records does on Salesforce Metadata Mcp

AI agents call sf_search_records 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.

RISK

Why sf_search_records is rated Low

This tool retrieves or queries data from Salesforce objects without creating, modifying, deleting, or executing side effects. SOSL is a read-only search mechanism. The blast radius of misuse is limited to information disclosure of accessible records.

From the tool's definition Tool performs search across Salesforce objects using SOSL (Salesforce Object Search Language). Description explicitly states it 'Searches across multiple Salesforce objects' with parameters for 'searchTerm' and optional 'fields list', indicating…

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_search_records 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_search_records, this is the rule to start with:

sf_search_records Allowed

sf_search_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_search_records": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_search_records call is checked against it from then on.

FAQ

Questions about sf_search_records

What does the sf_search_records tool do? +

Searches across multiple Salesforce objects using SOSL (Salesforce Object Search Language). SOSL uses the search index and is faster than SOQL for cross-object text searches. searchTerm: the text to search for objects: array of objects to search with optional fields list, e.g. [{ objectName:. 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_search_records? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_search_records: 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_search_records? +

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

Can I rate-limit sf_search_records? +

Yes. Add a rate_limit block to the sf_search_records 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_search_records completely? +

Set action: deny in the PolicyLayer policy for sf_search_records. 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_search_records? +

sf_search_records 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.

KEEP EXPLORING

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

This server

All 213 Salesforce Metadata tools →

Across the catalogue

search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server →search_channel on YouTube MCP Server →hybrid_search on Azure AI Agent Service + Azure AI Search MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →