🧠LLM-POWERED: Search with expanded terms for better semantic matching. Use this after expand_search_query to search with both the original query AND expanded keywords. This combines: - Original user query - LLM-generated expanded terms - Category filtering Returns more relevant results for vibe...
AI agents call semantic_search_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.
semantic_search_docs is a search and retrieval tool that queries existing documentation without side effects. It takes a user query, expands search terms for semantic matching, and returns documentation results. No data is created, modified, deleted, or executed. This is a pure Read operation with low blast radius—misuse would only retrieve documentation the user likely has legitimate access to anyway.
From the tool's definition Tool description explicitly states it 'search[es]' and 'returns more relevant results' with no mention of modification, deletion, execution, or financial operations. It queries documentation across Salesforce developer documents using semantic matching.
Documented attack patterns abuse exactly the kind of access semantic_search_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 semantic_search_docs:
{
"version": "1",
"default": "deny",
"tools": {
"semantic_search_docs": {}
}
}semantic_search_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.
🧠LLM-POWERED: Search with expanded terms for better semantic matching. Use this after expand_search_query to search with both the original query AND expanded keywords. This combines: - Original user query - LLM-generated expanded terms - Category filtering Returns more relevant results for vibe-style questions. 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 semantic_search_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.
semantic_search_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 semantic_search_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 semantic_search_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.
semantic_search_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.