sf_list_mcp_tools
Lists all tools currently registered in a given MCP server project by reading and parsing its src/index.ts file. Returns the tool names in the order they are registered. Use to audit what tools exist before adding new ones.
This record as markdown: /tools/io-github-semwalajay83-sem-salesforce-metadata-mcp/sf-list-mcp-tools.md
What sf_list_mcp_tools does on Salesforce Metadata Mcp
AI agents call sf_list_mcp_tools 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.
Why sf_list_mcp_tools is rated Low
This tool queries and retrieves information about registered tools by parsing a configuration file. It has no side effects, creates no data, and executes no external operations. It is purely informational for auditing purposes, making it a Read operation with low severity.
From the tool's definition 'Lists all tools currently registered in a given MCP server project by reading and parsing its src/index.ts file' — reads and returns data without modification
Attacks that exploit this kind of access
The rule that runs sf_list_mcp_tools 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_list_mcp_tools, this is the rule to start with:
sf_list_mcp_tools is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Salesforce Metadata Mcp, apply this rule, and every sf_list_mcp_tools call is checked against it from then on.
Questions about sf_list_mcp_tools
Lists all tools currently registered in a given MCP server project by reading and parsing its src/index.ts file. Returns the tool names in the order they are registered. Use to audit what tools exist before adding new ones. It is categorised as a Read tool in the Salesforce Metadata Mcp MCP Server, which means it retrieves data without modifying state.
Register the Salesforce Metadata MCP server in PolicyLayer and add a rule for sf_list_mcp_tools: 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.
sf_list_mcp_tools 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 sf_list_mcp_tools 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 sf_list_mcp_tools. 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.
sf_list_mcp_tools 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.
More on Salesforce Metadata, and thousands of servers like it.
This server
Across the catalogue