List teams available to the configured API key.
AI agents call blawx_teams_list to retrieve information from Blawx MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns a list of teams accessible to the user; it performs no write, delete, execute, or financial operations. The blast radius is minimal—an agent using this tool can only discover which teams exist in the system, posing no risk of data loss, code execution, or resource consumption beyond a simple API call.
From the tool's definition Tool name 'blawx_teams_list' and description 'List teams available to the configured API key' indicate a read-only operation that retrieves and enumerates data without modification or side effects.
Attacks that exploit this kind of access
List teams available to the configured API key. It is categorised as a Read tool in the Blawx MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Blawx MCP Server MCP server in PolicyLayer and add a rule for blawx_teams_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 Blawx MCP Server. Nothing to install.
blawx_teams_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 blawx_teams_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 blawx_teams_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.
blawx_teams_list is provided by the Blawx MCP Server MCP server (lexpedite/blawx_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 →