Create a new test scenario for an agent. Creates a scenario with a test case from a user message. IMPORTANT: Before calling this tool, confirm the scenario details with the user. Present the proposed name, description, user message, and expected tools — let them review and adjust before creatin...
Part of the Invarium MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents use invarium_create_scenario to create or modify resources in Invarium. 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 invarium_create_scenario repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Invarium.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
tools:
invarium_create_scenario:
rules:
- action: allow
rate_limit:
max: 30
window: 60See the full Invarium policy for all 19 tools.
Agents calling write-class tools like invarium_create_scenario have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.
Create a new test scenario for an agent. Creates a scenario with a test case from a user message. IMPORTANT: Before calling this tool, confirm the scenario details with the user. Present the proposed name, description, user message, and expected tools — let them review and adjust before creating. Do NOT create multiple scenarios in a batch without the user approving each one. Args: agent_name: Name of the agent to create the scenario for. name: Name/title of the scenario. description: Optional description of what this scenario tests. user_message: The input message the agent should handle (required). expected_tools: JSON array of tool names expected to be called, e.g. '["search", "fetch"]'. expected_behavior: Optional description of expected agent behavior. complexity: Scenario complexity — "simple", "complex", or "edge_case" (default: "simple"). tags: JSON array of tag strings, e.g. '["auth", "smoke"]'. Returns: A confirmation string with the new scenario ID, or an error message.. It is categorised as a Write tool in the Invarium MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Add a rule in your Intercept YAML policy under the tools section for invarium_create_scenario. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Invarium MCP server.
invarium_create_scenario 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 invarium_create_scenario rule in your Intercept 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 Intercept policy for invarium_create_scenario. 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.
invarium_create_scenario is provided by the Invarium MCP server (invarium-ai/invarium). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept