l402-credentials
List all stored L402 credentials. Shows origin, cached credit balance, and server type. Balance values are cached and may be stale; check lastUsed timestamp.
This record as markdown: /tools/dev-forgesworn-402-mcp/l402-credentials.md
What l402-credentials does on 402
AI agents call l402-credentials to retrieve information from 402 without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why l402-credentials is rated Low
The tool retrieves and displays stored credential metadata (origin, cached balances, timestamps) without side effects. While credentials themselves are sensitive, this tool only lists and reads them; it does not create, modify, delete, or execute actions. It is a straightforward inventory/query operation, classified as Read.
From the tool's definition Tool description states it 'List[s] all stored L402 credentials' and 'Shows origin, cached credit balance, and server type.' These are read-only query operations with no modification, deletion, or execution of code.
Attacks that exploit this kind of access
The rule that runs l402-credentials safely
PolicyLayer is an MCP gateway: it sits between your AI agents and 402, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For l402-credentials, this is the rule to start with:
l402-credentials is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect 402, apply this rule, and every l402-credentials call is checked against it from then on.
Questions about l402-credentials
List all stored L402 credentials. Shows origin, cached credit balance, and server type. Balance values are cached and may be stale; check lastUsed timestamp. It is categorised as a Read tool in the 402 MCP Server, which means it retrieves data without modifying state.
Register the 402 MCP server in PolicyLayer and add a rule for l402-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 402. Nothing to install.
l402-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 l402-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 l402-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.
l402-credentials is provided by the 402 MCP server (402-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on 402, and thousands of servers like it.
This server
Across the catalogue