sf_query_records

SERVERSalesforce Metadata Mcp SOURCEsalesforce-metadata-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-query-records.md

WHAT IT DOES

What sf_query_records does on Salesforce Metadata Mcp

AI agents call sf_query_records to retrieve information from Salesforce Metadata Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why sf_query_records is rated Low

SOQL is a read-only query language for Salesforce; this tool retrieves data without modifying it. Severity is medium because it could expose sensitive org data (PII, financial records, credentials stored in custom objects) if misused by an AI agent with broad query access.

From the tool's definition Executes a SOQL query against the org and returns matching records... Use for reading data, checking existing records before creating, or verifying changes.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs sf_query_records safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Salesforce Metadata Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sf_query_records, this is the rule to start with:

sf_query_records Allowed

sf_query_records is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "sf_query_records": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_query_records call is checked against it from then on.

FAQ

Questions about sf_query_records

What does the sf_query_records tool do? +

Executes a SOQL query against the org and returns matching records. Provide either a full SOQL string (soql param) or individual parameters (objectApiName, fields, whereClause, orderBy, limit). Use for reading data, checking existing records before creating, or verifying changes. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on sf_query_records? +

Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_query_records: 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 Metadata Mcp. Nothing to install.

What risk level is sf_query_records? +

sf_query_records is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit sf_query_records? +

Yes. Add a rate_limit block to the sf_query_records 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.

How do I block sf_query_records completely? +

Set action: deny in the PolicyLayer policy for sf_query_records. 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.

What MCP server provides sf_query_records? +

sf_query_records is provided by the Salesforce Metadata MCP server (salesforce-metadata-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Salesforce Metadata, and thousands of servers like it.

This server

All 213 Salesforce Metadata tools →

Across the catalogue

claude_query on Claude Bridge → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →