get_org_limits

THE RISK

Low Risk

Why get_org_limits needs a policy

This tool retrieves read-only information about Salesforce organization limits (such as API call limits, storage limits, concurrent user limits, etc.). It performs a GET operation against the Salesforce REST API to fetch existing data. There is no capability to modify, delete, or execute code, and no financial impact.

From the tool's definition Tool name 'get_org_limits' and description 'Get organization limits information from Salesforce REST API' indicate a retrieval operation that queries organizational metadata without modification or side effects.

Documented attack patterns abuse exactly the kind of access get_org_limits gives an agent:

POLICY

How to control get_org_limits

PolicyLayer is an MCP gateway — it sits between your AI agents and Salesforce, and nothing reaches the server without passing your rules. This is the rule we recommend for get_org_limits:

policy.json

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

get_org_limits is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Salesforce — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Salesforce tools

Destructive delete_apex_class Delete an Apex class (use with caution) Execute call_rest_api Make a generic REST API call to Salesforce (supports GET, POST, PATCH, DELETE) Execute execute_tooling_query Execute SOQL queries against Tooling API Execute run_tests Execute Apex tests Write create_apex_class Create a new Apex class Write update_apex_class Update the source code of an existing Apex class Read analyze_soql_performance Analyze SOQL query performance Read check_apex_sharing Check Apex class sharing declarations

All 25 Salesforce tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_org_limits

What does the get_org_limits tool do? +

Get organization limits information from Salesforce REST API. It is categorised as a Read tool in the Salesforce MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_org_limits? +

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

What risk level is get_org_limits? +

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

Can I rate-limit get_org_limits? +

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

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

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

Enforce policy on every Salesforce tool call.

Start from Salesforce, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →