List all configured providers (does not show keys)
AI agents call creds_list to retrieve information from ML Lab MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries the list of configured credential providers without exposing actual keys or making modifications. It has no side effects, cannot modify data, and presents no execution or destructive risk. The explicit note that it 'does not show keys' further confirms it is a safe read operation.
From the tool's definition Tool name 'creds_list' and description 'List all configured providers (does not show keys)' indicate retrieval-only functionality with no sensitive data exposure or side effects.
Attacks that exploit this kind of access
List all configured providers (does not show keys). It is categorised as a Read tool in the ML Lab MCP MCP Server, which means it retrieves data without modifying state.
Register the ML Lab MCP server in PolicyLayer and add a rule for creds_list: 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 ML Lab MCP. Nothing to install.
creds_list 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 creds_list 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 creds_list. 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.
creds_list is provided by the ML Lab MCP server (pushpullcommitpush/ml-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 →