Get list of Teams that you are a member of. WORKFLOW: Use returned team_id with get_team_channels. Returns: Array of team objects with id, displayName, description, and memberCount.
AI agents call get_teams to retrieve information from Microsoft Graph MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
get_teams is a straightforward data retrieval function that lists Teams membership. It queries existing data without altering, creating, deleting, or executing operations. The severity is low because enumeration of Teams the user is already a member of has minimal blast radius; this is contextual data needed for navigation within the user's own workspace.
From the tool's definition Tool returns 'Array of team objects with id, displayName, description, and memberCount' — purely retrieving/listing data with no modification, deletion, or side effects. No write, execute, destructive, or financial operations are performed.
Documented attack patterns abuse exactly the kind of access get_teams gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Microsoft Graph MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_teams:
{
"version": "1",
"default": "deny",
"tools": {
"get_teams": {}
}
}get_teams is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Get list of Teams that you are a member of. WORKFLOW: Use returned team_id with get_team_channels. Returns: Array of team objects with id, displayName, description, and memberCount. It is categorised as a Read tool in the Microsoft Graph MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Microsoft Graph MCP Server MCP server in PolicyLayer and add a rule for get_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 Microsoft Graph MCP Server. Nothing to install.
get_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 get_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 get_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.
get_teams is provided by the Microsoft Graph MCP Server MCP server (marlonluo2018/microsoft_graph_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Microsoft Graph MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
19 Microsoft Graph MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.