describe_tooling_object

THE RISK

Low Risk

Why describe_tooling_object needs a policy

This tool retrieves descriptive metadata about Tooling API object schemas, analogous to DESCRIBE TABLE operations. It has no side effects, does not execute code, does not modify data, and does not delete anything. The blast radius of misuse is minimal—an agent could only gain information about available Salesforce metadata structures.

From the tool's definition Tool name and description indicate schema/metadata retrieval: 'Get schema information for Tooling API objects'.

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

POLICY

How to control describe_tooling_object

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 describe_tooling_object:

policy.json

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

describe_tooling_object 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 describe_tooling_object

What does the describe_tooling_object tool do? +

Get schema information for Tooling API objects. 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 describe_tooling_object? +

Register the Salesforce MCP server in PolicyLayer and add a rule for describe_tooling_object: 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 describe_tooling_object? +

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

Can I rate-limit describe_tooling_object? +

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

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

describe_tooling_object 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 →