List all stored credentials. Returns metadata only - no passwords or API keys are exposed.
AI agents call list_credentials to retrieve information from Chrome MCP Server (Security Hardened) without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves credential metadata without modification or deletion. While exposure of credential metadata (usernames, service names, creation dates) could be sensitive in an enterprise context and enable social engineering or targeted attacks, the tool itself performs only a read operation.
From the tool's definition Tool name 'list_credentials' and description state it 'List[s] all stored credentials' and 'Returns metadata only - no passwords or API keys are exposed.' This is a query/retrieval operation with no side effects.
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 Chrome MCP Server (Security Hardened), 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 stored credentials. Returns metadata only - no passwords or API keys are exposed. It is categorised as a Read tool in the Chrome MCP Server (Security Hardened) MCP Server, which means it retrieves data without modifying state.
Register the Chrome MCP Server (Security Hardened) 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 Chrome MCP Server (Security Hardened). 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 Chrome MCP Server (Security Hardened) MCP server (pantheon-security/chrome-mcp-secure). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Chrome MCP Server (Security Hardened), add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
7 Chrome MCP Server (Security Hardened) tools catalogued and risk-classified — across an index of 43,000+ MCP servers.