New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

list_provider_endpoints

Inspect a provider endpoint/action catalog before drafting a workflow. Returns available actions, auth mode, required scopes, rate-limit hints, and policy constraints when the registry exposes them.

SERVERStarfield SOURCE@adrata/starfield-mcp
Low RISK CLASS
Category Read
Parameters 21 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adrata-starfield-mcp/list-provider-endpoints.md

What list_provider_endpoints does on Starfield

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

ParameterTypeRequiredDescription
search string Optional endpoint search string
provider string Yes Provider slug, for example salesforce, hubspot, heyreach, or a custom provider slug

Parameters from the server's own tool schema.

Why list_provider_endpoints is rated Low

Even though list_provider_endpoints only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about list_provider_endpoints

What does the list_provider_endpoints tool do? +

Inspect a provider endpoint/action catalog before drafting a workflow. Returns available actions, auth mode, required scopes, rate-limit hints, and policy constraints when the registry exposes them. It is categorised as a Read tool in the Starfield MCP Server, which means it retrieves data without modifying state.

What parameters does list_provider_endpoints accept? +

list_provider_endpoints accepts 2 parameters: search, provider. Required: provider. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on list_provider_endpoints? +

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

What risk level is list_provider_endpoints? +

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

Can I rate-limit list_provider_endpoints? +

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

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

list_provider_endpoints is provided by the Starfield MCP server (@adrata/starfield-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Starfield, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Starfield's. Pull the full record:

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.