Make a generic REST API call to Salesforce (supports GET, POST, PATCH, DELETE)
AI agents invoke call_rest_api to trigger actions in Salesforce. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool supports arbitrary HTTP methods including DELETE and PATCH against the Salesforce API, meaning it can read, write, modify, or irreversibly delete any Salesforce data depending on the arguments passed.
From the tool's definition Make a generic REST API call to Salesforce (supports GET, POST, PATCH, DELETE)
Documented attack patterns abuse exactly the kind of access call_rest_api gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce, and nothing reaches the server without passing your rules. This is the rule we recommend for call_rest_api:
{
"version": "1",
"default": "deny",
"tools": {
"call_rest_api": {
"limits": [
{
"counter": "call_rest_api_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} call_rest_api stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Make a generic REST API call to Salesforce (supports GET, POST, PATCH, DELETE). It is categorised as a Execute tool in the Salesforce MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Salesforce MCP server in PolicyLayer and add a rule for call_rest_api: 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. Nothing to install.
call_rest_api is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the call_rest_api 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 call_rest_api. 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.
call_rest_api is provided by the Salesforce MCP server (ryu-727/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Salesforce, 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.
25 Salesforce tools catalogued and risk-classified — across an index of 43,000+ MCP servers.