List all tracked providers, with optional category filter.
AI agents call list_providers to retrieve information from Sovereignty Scan without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays provider data without modifying, executing code, deleting, or committing financial obligations. It is a straightforward informational read operation with minimal security risk—an AI agent could at worst retrieve a list of provider names, which is already public documentation. No destructive or state-changing actions are possible.
From the tool's definition Tool name 'list_providers' and description 'List all tracked providers' indicate a retrieval operation with no side effects. The optional category filter further confirms this is a query/search capability.
Attacks that exploit this kind of access
List all tracked providers, with optional category filter. It is categorised as a Read tool in the Sovereignty Scan MCP Server, which means it retrieves data without modifying state.
Register the Sovereignty Scan MCP server in PolicyLayer and add a rule for list_providers: 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 Sovereignty Scan. Nothing to install.
list_providers 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 list_providers 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 list_providers. 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.
list_providers is provided by the Sovereignty Scan MCP server (mightbesaad/sovereignty-scan-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →