List all available SObjects in the Salesforce org.
AI agents call salesforce_list_objects to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query of Salesforce metadata (SObjects), returning available schema information. It has no side effects, does not create, modify, or delete data, and does not execute code or commands. The blast radius of misuse is minimal—an attacker gains only visibility into the org's data structure, which may aid reconnaissance but causes no direct harm.
From the tool's definition Tool name 'salesforce_list_objects' and description 'List all available SObjects in the Salesforce org' indicate a retrieval/query operation that returns metadata about available objects without modifying, deleting, or executing external operations.
Attacks that exploit this kind of access
List all available SObjects in the Salesforce org. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
Register the Integrations MCP server in PolicyLayer and add a rule for salesforce_list_objects: 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 Integrations MCP. Nothing to install.
salesforce_list_objects 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 salesforce_list_objects 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_list_objects. 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_list_objects is provided by the Integrations MCP server (shriram-vasudevan/integrations-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 →