List stored users and tokens from a token store
AI agents call list_user to retrieve information from API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool queries and returns stored user and token data without modifying or deleting it. Although exposure of user and token information could enable authentication bypass if misused by an attacker, in the context of an MCP tool exposed to an AI agent, this is a read operation that retrieves data.
From the tool's definition Tool name is "list_user" and description states "List stored users and tokens from a token store" — this is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List stored users and tokens from a token store. It is categorised as a Read tool in the API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the API MCP Server MCP server in PolicyLayer and add a rule for list_user: 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 API MCP Server. Nothing to install.
list_user 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_user 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_user. 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_user is provided by the API MCP Server MCP server (vilasone455/api-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 →