contract-testing_get_provider_states
Retrieve the states of a specific provider Parameters: - provider (string) *required*: name of the provider to retrieve states for
This record as markdown: /tools/smartbear-mcp/contract-testing-get-provider-states.md
What contract-testing_get_provider_states does on SmartBear MCP
AI agents call contract-testing_get_provider_states 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 |
|---|---|---|---|
provider | string | Yes | name of the provider to retrieve states for |
Parameters from the server's own tool schema.
Why contract-testing_get_provider_states is rated Low
This tool retrieves provider state information from a contract-testing system (PactFlow). It performs a read-only operation that queries existing data without creating, modifying, deleting, or executing anything. The single parameter (provider name) is used only to filter the retrieval, not to trigger external operations or mutations. This is a straightforward Read category tool with low severity risk.
From the tool's definition Tool name includes 'get_provider_states' and description states 'Retrieve the states of a specific provider' — both indicate a query/retrieval operation with no modification.
Attacks that exploit this kind of access
The rule that runs contract-testing_get_provider_states 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_provider_states, this is the rule to start with:
contract-testing_get_provider_states 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_provider_states call is checked against it from then on.
Questions about contract-testing_get_provider_states
Retrieve the states of a specific provider Parameters: - provider (string) *required*: name of the provider to retrieve states for. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_get_provider_states accepts 1 parameter: provider. Required: provider. 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_provider_states: 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_provider_states 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_provider_states 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_provider_states. 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_provider_states 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