Get specific Salesforce API reference documentation. Supports: REST API, SOAP API, Metadata API, Bulk API 2.0, Tooling API, Streaming API, Chatter REST API, Analytics REST API, and more. Provide the API name and optionally a specific endpoint or resource.
AI agents call get_api_reference 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 performs information retrieval from a documentation database. It does not create, modify, delete, execute, or commit any transactions. The worst-case misuse is retrieving API documentation an attacker shouldn't access, a minimal information disclosure risk that does not match higher-severity categories. Confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool retrieves 'specific Salesforce API reference documentation' with no mention of modification, deletion, or execution capabilities. It returns documentation for REST API, SOAP API, Metadata API, etc.
Documented attack patterns abuse exactly the kind of access get_api_reference 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 get_api_reference:
{
"version": "1",
"default": "deny",
"tools": {
"get_api_reference": {}
}
}get_api_reference 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.
Get specific Salesforce API reference documentation. Supports: REST API, SOAP API, Metadata API, Bulk API 2.0, Tooling API, Streaming API, Chatter REST API, Analytics REST API, and more. Provide the API name and optionally a specific endpoint or resource. 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 get_api_reference: 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.
get_api_reference 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 get_api_reference 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 get_api_reference. 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.
get_api_reference 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.