AI agents call list_teams to retrieve information from RoadBoard 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 information about teams the current user belongs to. It performs no write, delete, execution, or financial operations. The blast radius of misuse is minimal—an agent could enumerate team membership but cannot modify state, execute actions, or cause harm. Classification as Read is appropriate.
From the tool's definition Tool name 'list_teams' and description 'List teams' indicate data retrieval with no modification. The phrase 'each with its slug and the caller' confirms it returns metadata about existing teams without side effects.
Attacks that exploit this kind of access
List teams the current user belongs to, each with its slug and the caller. It is categorised as a Read tool in the RoadBoard MCP Server, which means it retrieves data without modifying state.
Register the RoadBoard MCP server in PolicyLayer and add a rule for list_teams: 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 RoadBoard. Nothing to install.
list_teams 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_teams 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_teams. 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_teams is provided by the RoadBoard MCP server (maless88/roadboard). 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 →