ALWAYS call this first for any RF scenario request. Returns block schemas, composition rules, constraints, and a reference example payload. YOU must compose your own graph/project using this guidance, then call rfix_export_rfix_project. Do NOT search the filesystem for blocks or examples — this t...
Risk signalsBulk/mass operation — affects multiple targets
Part of the RFix server.
Free to start. No card required.
AI agents use rfix_plan_scenario to create or modify resources in RFix. 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 rfix_plan_scenario 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 RFix.
Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.
{
"version": "1",
"default": "deny",
"tools": {
"rfix_plan_scenario": {
"limits": [
{
"counter": "rfix_plan_scenario_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}See the full RFix policy for all 3 tools.
These attack patterns abuse exactly the kind of access rfix_plan_scenario 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.
ALWAYS call this first for any RF scenario request. Returns block schemas, composition rules, constraints, and a reference example payload. YOU must compose your own graph/project using this guidance, then call rfix_export_rfix_project. Do NOT search the filesystem for blocks or examples — this tool returns everything needed.. It is categorised as a Write tool in the RFix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the RFix MCP server in PolicyLayer and add a rule for rfix_plan_scenario: 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 RFix. Nothing to install.
rfix_plan_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 rfix_plan_scenario 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 rfix_plan_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.
rfix_plan_scenario is provided by the RFix MCP server (https://mcp.rfix.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 3 RFix 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.