List API keys associated with the master account (or with a specific store, if the upstream key supports it).\n\n
AI agents call wafle_auth_keys_list to retrieve information from wafle MCP server 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 API keys, which is fundamentally a read operation. However, API keys are sensitive authentication credentials whose exposure could allow unauthorized access to the wafle platform and compromise store/account security. While the tool itself performs no destructive or modifying action, the sensitivity of the data retrieved (API keys) elevates severity to 'high' rather than 'low'.
From the tool's definition Tool name contains 'list' and description states 'List API keys associated with the master account (or with a specific store, if the upstream key supports it).' The verb 'List' is a retrieval operation with no side effects.
Attacks that exploit this kind of access
List API keys associated with the master account (or with a specific store, if the upstream key supports it).\n\n. It is categorised as a Read tool in the wafle MCP server MCP Server, which means it retrieves data without modifying state.
Register the wafle MCP server MCP server in PolicyLayer and add a rule for wafle_auth_keys_list: 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 wafle MCP server. Nothing to install.
wafle_auth_keys_list 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 wafle_auth_keys_list 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 wafle_auth_keys_list. 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.
wafle_auth_keys_list is provided by the wafle MCP server MCP server (the33warehouse-tech/wafle-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 →