Count Salesforce records
AI agents call count to retrieve information from Salesforce MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The count operation is a read-only query that retrieves numeric summaries of records. It has no side effects, does not create, modify, or delete data, and does not execute code or trigger external operations. The blast radius of misuse is minimal—an attacker can only learn record counts, which is non-sensitive compared to other Salesforce operations available on this server.
From the tool's definition Tool name 'count' with description 'Count Salesforce records' indicates a query operation that retrieves aggregated record counts without modifying data.
Attacks that exploit this kind of access
Count Salesforce records. It is categorised as a Read tool in the Salesforce MCP MCP Server, which means it retrieves data without modifying state.
Register the Salesforce MCP server in PolicyLayer and add a rule for count: 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. Nothing to install.
count 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 count 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 count. 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.
count is provided by the Salesforce MCP server (jpmonette/salesforce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
count is one line of Salesforce's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →