Low Risk

get_team_members

Retrieves a list of all users who are members of a specific team, including their basic information and status. Use this to audit team membership and understand who has team-based access.

How to control get_team_members ↓

What get_team_members does on Dataverse MCP Server

AI agents call get_team_members to retrieve information from Dataverse MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_team_members needs a policy

This tool queries and returns team membership data without modifying, deleting, or executing any operations. It is a straightforward data retrieval operation used for auditing purposes, with no destructive, financial, or code-execution capabilities.

From the tool's definition Tool name 'get_team_members' and description 'Retrieves a list of all users' — retrieval operation with no side effects. Description explicitly states 'Use this to audit team membership', confirming read-only intent.

Documented attack patterns abuse exactly the kind of access get_team_members gives an agent:

How to control get_team_members

PolicyLayer is an MCP gateway — it sits between your AI agents and Dataverse MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_team_members:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_team_members": {}
  }
}

get_team_members is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Dataverse MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_team_members

What does the get_team_members tool do? +

Retrieves a list of all users who are members of a specific team, including their basic information and status. Use this to audit team membership and understand who has team-based access. It is categorised as a Read tool in the Dataverse MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_team_members? +

Register the Dataverse MCP Server MCP server in PolicyLayer and add a rule for get_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 Dataverse MCP Server. Nothing to install.

What risk level is get_team_members? +

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

Can I rate-limit get_team_members? +

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

How do I block get_team_members completely? +

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

What MCP server provides get_team_members? +

get_team_members is provided by the Dataverse MCP Server MCP server (mwhesse/dataverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dataverse MCP Server tool call.

Start from Dataverse 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.

71 Dataverse MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.