contract-testing_get_integrations_by_team
Retrieve all consumer-provider integrations belonging to a specific team. Parameters: - teamId (string) *required*: UUID of the team
This record as markdown: /tools/smartbear-mcp/contract-testing-get-integrations-by-team.md
What contract-testing_get_integrations_by_team does on SmartBear MCP
AI agents call contract-testing_get_integrations_by_team 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 |
Parameters from the server's own tool schema.
Why contract-testing_get_integrations_by_team is rated Low
This tool queries and returns integration data for a given team. It performs no write, deletion, execution, or financial operations. The operation is read-only and carries minimal security risk unless the integration data itself contains highly sensitive credentials (which would be a data governance issue, not a tool capability issue). Confidence is high due to clear retrieval semantics in both name and description.
From the tool's definition Tool name contains 'get_integrations' and description states 'Retrieve all consumer-provider integrations belonging to a specific team' — both indicate a retrieval operation with no modification or execution.
Attacks that exploit this kind of access
The rule that runs contract-testing_get_integrations_by_team 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_get_integrations_by_team, this is the rule to start with:
contract-testing_get_integrations_by_team 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_get_integrations_by_team call is checked against it from then on.
Questions about contract-testing_get_integrations_by_team
Retrieve all consumer-provider integrations belonging to a specific team. Parameters: - teamId (string) *required*: UUID of the team. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_get_integrations_by_team accepts 1 parameter: teamId. Required: teamId. 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_get_integrations_by_team: 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_get_integrations_by_team 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_get_integrations_by_team 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_get_integrations_by_team. 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_get_integrations_by_team 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