AI agents call teams_list_team_members to retrieve information from Sage MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves team membership information. It performs a read-only operation that neither modifies data nor triggers external actions. The blast radius of misuse is minimal—an attacker might gain visibility into team composition but cannot alter permissions, delete members, or perform financial transactions. Standard read-operation classification applies.
From the tool's definition Tool name 'teams_list_team_members' and description 'List members of a team' indicate a retrieval operation with no modification or side effects.
Documented attack patterns abuse exactly the kind of access teams_list_team_members gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Sage MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for teams_list_team_members:
{
"version": "1",
"default": "deny",
"tools": {
"teams_list_team_members": {}
}
}teams_list_team_members 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.
List members of a team. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP server in PolicyLayer and add a rule for teams_list_team_members: 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 Sage MCP. Nothing to install.
teams_list_team_members 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 teams_list_team_members 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 teams_list_team_members. 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.
teams_list_team_members is provided by the Sage MCP server (sagemcp/sagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 359 Sage MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
359 Sage MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.