contract-testing_admin_get_team_user
Check if a specific user is a member of a team (admin). Parameters: - teamId (string) *required*: UUID of the team - userId (string) *required*: UUID of the user
This record as markdown: /tools/smartbear-mcp/contract-testing-admin-get-team-user.md
What contract-testing_admin_get_team_user does on SmartBear MCP
AI agents call contract-testing_admin_get_team_user to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
teamId | string | Yes | UUID of the team |
userId | string | Yes | UUID of the user |
Parameters from the server's own tool schema.
Why contract-testing_admin_get_team_user is rated Low
This tool performs a simple membership lookup query. It takes two identifiers (teamId, userId) and returns whether a user belongs to a team. No data is created, modified, deleted, or executed. The blast radius of misuse is low — an attacker could enumerate team memberships but cannot escalate privileges, modify systems, or access sensitive data beyond the boolean membership status.
From the tool's definition Tool description states 'Check if a specific user is a member of a team (admin)' — this is a query operation that retrieves membership information without modifying data or triggering external actions.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs contract-testing_admin_get_team_user safely
PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_admin_get_team_user, this is the rule to start with:
contract-testing_admin_get_team_user is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_admin_get_team_user call is checked against it from then on.
Questions about contract-testing_admin_get_team_user
Check if a specific user is a member of a team (admin). Parameters: - teamId (string) *required*: UUID of the team - userId (string) *required*: UUID of the user. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_admin_get_team_user accepts 2 parameters: teamId, userId. Required: teamId, userId. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_admin_get_team_user: 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 SmartBear MCP. Nothing to install.
contract-testing_admin_get_team_user 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 contract-testing_admin_get_team_user 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 contract-testing_admin_get_team_user. 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.
contract-testing_admin_get_team_user is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on SmartBear, and thousands of servers like it.
This server
Across the catalogue