Makes a direct REST API call to Salesforce
AI agents invoke restful to trigger actions in Salesforce MCP Server. 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.
While the tool itself is not inherently destructive or financial, it acts as a generic execution interface to Salesforce's REST API surface. An AI agent could use this tool to invoke any endpoint (create, delete, execute scripts, etc.) based on arguments provided. This makes it Execute-category rather than Write or Read, since the effects depend entirely on which REST endpoint is called and what payload is sent.
From the tool's definition The tool description states it 'Makes a direct REST API call to Salesforce', which enables arbitrary API operations without constrained parameters.
Attacks that exploit this kind of access
Makes a direct REST API call to Salesforce. It is categorised as a Execute tool in the Salesforce MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Salesforce MCP Server MCP server in PolicyLayer and add a rule for restful: 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 MCP Server. Nothing to install.
restful 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 restful 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 restful. 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.
restful is provided by the Salesforce MCP Server MCP server (steffensbola/salesforce-mcp-ts). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →