windsurf_list_members

List team members (stub -- API not publicly available,

SERVERSage MCP SOURCEsagemcp/sagemcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/sagemcp-sagemcp/windsurf-list-members.md

WHAT IT DOES

What windsurf_list_members does on Sage MCP

AI agents call windsurf_list_members to retrieve information from Sage MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why windsurf_list_members is rated Low

This tool retrieves or queries team member information with no capability to modify, delete, or execute operations. The read-only nature and stub status make it low risk even if it were fully implemented. Confidence is reduced slightly due to the stub status and vague description, but the 'list' operation clearly indicates a Read category.

From the tool's definition Tool name contains 'list' and description states 'List team members' — retrieves data without modification or side effects. The '(stub -- API not publicly available)' notation indicates this is a non-functional placeholder.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs windsurf_list_members safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Sage MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For windsurf_list_members, this is the rule to start with:

windsurf_list_members Allowed

windsurf_list_members is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "windsurf_list_members": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Sage MCP, apply this rule, and every windsurf_list_members call is checked against it from then on.

FAQ

Questions about windsurf_list_members

What does the windsurf_list_members tool do? +

List team members (stub -- API not publicly available,. It is categorised as a Read tool in the Sage MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on windsurf_list_members? +

Register the Sage MCP server in PolicyLayer and add a rule for windsurf_list_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.

What risk level is windsurf_list_members? +

windsurf_list_members is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit windsurf_list_members? +

Yes. Add a rate_limit block to the windsurf_list_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.

How do I block windsurf_list_members completely? +

Set action: deny in the PolicyLayer policy for windsurf_list_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.

What MCP server provides windsurf_list_members? +

windsurf_list_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.

KEEP EXPLORING

More on Sage, and thousands of servers like it.

This server

All 359 Sage tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →