BlazeMeter Service Virtualization MCP integration for AI agents.
Connect AI agents to BlazeMeter Service Virtualization through 3 structured actions, including get service mock template, update service mock template, and l…
- ACTION CONTRACTS
- 3
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the BlazeMeter Service Virtualization integration exposes
The BlazeMeter Service Virtualization Agent App exposes 3 provider-backed actions for developer tools work. Its current contract lets an authorized agent get one blazemeter service virtualization service mock template by template id, update json-safe configuration fields for one blazemeter service mock template, and list blazemeter service virtualization service mock templates in a workspace. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected BlazeMeter Service Virtualization account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real BlazeMeter Service Virtualization capabilities.
Showing 3 of 3 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_service_mock_templateREADGet one BlazeMeter Service Virtualization service mock template by template ID.
INPUTS: workspaceId / templateId
update_service_mock_templateWRITEUpdate JSON-safe configuration fields for one BlazeMeter service mock template.
INPUTS: workspaceId / templateId / name / description / thinkTime
list_service_mock_templatesREADList BlazeMeter Service Virtualization service mock templates in a workspace.
INPUTS: workspaceId
INPUT CONTRACTS
Know what the action needs before it runs.
get_service_mock_template
workspaceIdREQUIRED- The BlazeMeter workspace ID that contains service mock templates.
templateIdREQUIRED- The BlazeMeter service mock template ID.
update_service_mock_template
workspaceIdREQUIRED- The BlazeMeter workspace ID that contains service mock templates.
templateIdREQUIRED- The BlazeMeter service mock template ID.
nameOPTIONAL- The updated service mock template name.
descriptionOPTIONAL- The updated service mock template description.
thinkTimeOPTIONAL- The synthetic delay between test steps in milliseconds.
list_service_mock_templates
workspaceIdREQUIRED- The BlazeMeter workspace ID that contains service mock templates.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Service Mock Template
Get one BlazeMeter Service Virtualization service mock template by template ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_service_mock_templateControl Update Service Mock Template
Update JSON-safe configuration fields for one BlazeMeter service mock template. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
update_service_mock_templateVerify with List Service Mock Templates
List BlazeMeter Service Virtualization service mock templates in a workspace. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_service_mock_templatesSAFETY BOUNDARY
Operate BlazeMeter Service Virtualization with explicit limits
- Authorize BlazeMeter Service Virtualization with API key and grant only the provider access required by the selected actions.
- 1 action is change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in BlazeMeter Service Virtualization rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the BlazeMeter Service Virtualization task completed successfully.
CONNECTION MODEL
API key
BlazeMeter API secret used as the Basic Auth password. Create or copy API keys from the BlazeMeter API Keys settings page: https://a.blazemeter.com/app/#/settings/api-keys.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by BlazeMeter Service Virtualization.