List all AWS credentials/configs/profiles that are configured/usable on this machine
AI agents call list-credentials to retrieve information from Aws without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation as it retrieves and lists data (AWS credentials and configurations) without modifying or executing anything. However, the severity is high because exposed credentials can be used for unauthorized access to AWS resources, representing significant blast radius if an AI agent lists credentials and they are subsequently logged, exfiltrated, or misused.
From the tool's definition Tool name 'list-credentials' and description 'List all AWS credentials/configs/profiles that are configured/usable on this machine' indicate retrieval of sensitive credential information without modification.
Documented attack patterns abuse exactly the kind of access list-credentials gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Aws, and nothing reaches the server without passing your rules. This is the rule we recommend for list-credentials:
{
"version": "1",
"default": "deny",
"tools": {
"list-credentials": {}
}
}list-credentials is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all AWS credentials/configs/profiles that are configured/usable on this machine. It is categorised as a Read tool in the Aws MCP Server, which means it retrieves data without modifying state.
Register the Aws MCP server in PolicyLayer and add a rule for list-credentials: 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 Aws. Nothing to install.
list-credentials 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-credentials 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-credentials. 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-credentials is provided by the Aws MCP server (rafalwilinski/aws-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 Aws tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
3 Aws tools catalogued and risk-classified — across an index of 42,500+ MCP servers.