List saved ~/.claude.json profiles and the currently active one. Profiles let you switch between work/personal accounts or different orgs.
AI agents call list_profiles to retrieve information from Claude Code Toolkit 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 existing profile configuration data from the user's system without creating, modifying, or deleting any data. It is purely informational for observability and management purposes. The blast radius is minimal—exposing which profiles exist poses no direct operational risk.
From the tool's definition Tool name is 'list_profiles' and description explicitly states 'List saved ~/.claude.json profiles'. The verb 'list' and the action of retrieving profile information with no modification capability clearly indicates a read-only operation.
Documented attack patterns abuse exactly the kind of access list_profiles gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Claude Code Toolkit, and nothing reaches the server without passing your rules. This is the rule we recommend for list_profiles:
{
"version": "1",
"default": "deny",
"tools": {
"list_profiles": {}
}
} list_profiles 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 saved ~/.claude.json profiles and the currently active one. Profiles let you switch between work/personal accounts or different orgs. It is categorised as a Read tool in the Claude Code Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Claude Code Toolkit MCP server in PolicyLayer and add a rule for list_profiles: 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 Claude Code Toolkit. Nothing to install.
list_profiles 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_profiles 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_profiles. 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_profiles is provided by the Claude Code Toolkit MCP server (asifkibria/claude-code-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Claude Code Toolkit, 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.
40 Claude Code Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.