salesforce_query
AI agents invoke salesforce_query to trigger actions in WWIDE 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 name implies running queries against Salesforce, which could range from simple reads to executing arbitrary SOQL/SOSL that may include destructive operations. With an empty description, the exact capability is unknown, but query execution in Salesforce typically allows arbitrary data retrieval at minimum.
From the tool's definition Tool name 'salesforce_query' suggests query execution; description is empty and uninformative.
Attacks that exploit this kind of access
salesforce_query. It is categorised as a Execute tool in the WWIDE MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the WWIDE MCP Server MCP server in PolicyLayer and add a rule for salesforce_query: 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 WWIDE MCP Server. Nothing to install.
salesforce_query 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 salesforce_query 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 salesforce_query. 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.
salesforce_query is provided by the WWIDE MCP Server MCP server (kulvir88/salesforce-mcp). 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 →