Executes a Tooling API request
AI agents invoke tooling_execute 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.
The Tooling API in Salesforce enables deployment, metadata operations, and system-level configurations. While the tool description lacks specifics on what operations are permitted, the name and context indicate it executes arbitrary Tooling API requests—a classic Execute pattern.
From the tool's definition Tool description states 'Executes a Tooling API request' which invokes external Salesforce operations. Combined with sibling tools (apex_execute, create_record, delete_record, update_record, run_soql_query) that span Write, Execute, and Destructive…
Attacks that exploit this kind of access
Executes a Tooling API request. 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 tooling_execute: 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.
tooling_execute 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 tooling_execute 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 tooling_execute. 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.
tooling_execute 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 →