Set or update the steps in a test scenario. Each step references an API endpoint via bindId (apiDetailId). Steps are fully replaced — pass the complete steps array. Supports
Part of the Apidog Tests server.
Free to start. No card required.
AI agents use update_test_scenario_steps to create or modify resources in Apidog Tests. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.
Without a policy, an AI agent could call update_test_scenario_steps repeatedly, creating or modifying resources faster than any human could review. PolicyLayer's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Apidog Tests.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"update_test_scenario_steps": {
"limits": [
{
"counter": "update_test_scenario_steps_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full Apidog Tests policy for all 30 tools.
These attack patterns abuse exactly the kind of access update_test_scenario_steps gives an agent. Each links to the full case and the policy that stops it:
Other write tools across the catalogue. The same approach applies to each: rate-limit and validate the arguments.
Set or update the steps in a test scenario. Each step references an API endpoint via bindId (apiDetailId). Steps are fully replaced — pass the complete steps array. Supports. It is categorised as a Write tool in the Apidog Tests MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Apidog Tests MCP server in PolicyLayer and add a rule for update_test_scenario_steps: 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 Apidog Tests. Nothing to install.
update_test_scenario_steps is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the update_test_scenario_steps 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 update_test_scenario_steps. 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.
update_test_scenario_steps is provided by the Apidog Tests MCP server (@acabala/apidog-tests-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 30 Apidog Tests tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.