Search Salesforce documentation with relevance-ranked results. Searches across 360 official Salesforce PDF documents including: - Apex Developer Guide & Reference - REST API, SOAP API, Metadata API, Bulk API - Lightning Web Components (LWC) - Visualforce, SOQL/SOSL - Integration patterns, Securit...
AI agents call search_salesforce_docs to retrieve information from Salesforce Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and queries static documentation content with no side effects. It cannot modify data, execute code, delete records, or incur financial obligations. The worst misuse scenario—an AI agent searching for sensitive information in public documentation—carries minimal blast radius since the documentation is official and already published.
From the tool's definition Tool description states it 'Search[es] Salesforce documentation' and 'Returns document ID, relevant excerpts, and source information.' No modification, execution, deletion, or financial operations are described.
Documented attack patterns abuse exactly the kind of access search_salesforce_docs gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce Documentation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for search_salesforce_docs:
{
"version": "1",
"default": "deny",
"tools": {
"search_salesforce_docs": {}
}
}search_salesforce_docs is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Search Salesforce documentation with relevance-ranked results. Searches across 360 official Salesforce PDF documents including: - Apex Developer Guide & Reference - REST API, SOAP API, Metadata API, Bulk API - Lightning Web Components (LWC) - Visualforce, SOQL/SOSL - Integration patterns, Security guides - Release notes (last 10 years) Results are ranked by match density (how many search terms appear) combined with document priority. Returns document ID, relevant excerpts, and source information. It is categorised as a Read tool in the Salesforce Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Documentation MCP Server MCP server in PolicyLayer and add a rule for search_salesforce_docs: 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 Documentation MCP Server. Nothing to install.
search_salesforce_docs 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 search_salesforce_docs 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 search_salesforce_docs. 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.
search_salesforce_docs is provided by the Salesforce Documentation MCP Server MCP server (salesforcediariesbysanket/salesforce-docs-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce Documentation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Salesforce Documentation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.