query_records_to_file

Query records from a Salesforce SObject from a project and save to a file. This command allows you to execute a SOQL query against a specified Salesforce SObject in a given Org and save the results to a file. You can specify the SELECT clause (fields, functions like COUNT(), aggregations, etc.), ...

Server Salesforce CLI MCP Server perrynet/salesforce-cli-mcp-server
Category Read
Risk class Low
Parameters 00 required

What query_records_to_file does on Salesforce CLI MCP Server

AI agents call query_records_to_file to retrieve information from Salesforce CLI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why query_records_to_file needs a policy

This tool performs a read-only SOQL query against Salesforce and saves results to a file. SOQL is a SELECT-only query language with no DML capabilities, so it cannot modify or delete data. Writing to a local file is a minor side effect but the primary operation is data retrieval. The file write aspect is low risk in context. Severity is low as misuse only exposes data to an unintended file location.

From the tool's definition 'Query records from a Salesforce SObject' and 'execute a SOQL query against a specified Salesforce SObject' and 'save the results to a file'

Questions about query_records_to_file

What does the query_records_to_file tool do? +

Query records from a Salesforce SObject from a project and save to a file. This command allows you to execute a SOQL query against a specified Salesforce SObject in a given Org and save the results to a file. You can specify the SELECT clause (fields, functions like COUNT(), aggregations, etc.), an optional WHERE clause, and save the results in various formats. The results can be saved in CSV format by default, or in other formats if specified. IMPORTANT: Always execute the. It is categorised as a Read tool in the Salesforce CLI MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on query_records_to_file? +

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

What risk level is query_records_to_file? +

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

Can I rate-limit query_records_to_file? +

Yes. Add a rate_limit block to the query_records_to_file 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 query_records_to_file completely? +

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

query_records_to_file is provided by the Salesforce CLI MCP Server MCP server (perrynet/salesforce-cli-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.