This record as markdown: /tools/tjnull-ludus-fastmcp/update-range-config.md
What update_range_config does on Ludus FastMCP
AI agents use update_range_config to create or update resources in Ludus FastMCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Ludus FastMCP environment.
Why update_range_config is rated Medium
This tool modifies configuration state reversibly—configurations can be changed again without permanent data loss. It does not execute arbitrary code (Execute), delete data (Destructive), or move money (Financial). However, severity is high because misconfigured cyber range environments could degrade security testing integrity, affect multiple scenarios, or impact other users sharing the range.
From the tool's definition Tool name is 'update_range_config' with description 'Update range configuration.' The verb 'update' indicates modification of existing data.
Attacks that exploit this kind of access
The rule that runs update_range_config safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Ludus FastMCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For update_range_config, this is the rule to start with:
update_range_config stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Ludus FastMCP, apply this rule, and every update_range_config call is checked against it from then on.
Questions about update_range_config
Update range configuration. It is categorised as a Write tool in the Ludus FastMCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Ludus Fast MCP server in PolicyLayer and add a rule for update_range_config: 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 Ludus FastMCP. Nothing to install.
update_range_config 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_range_config 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_range_config. 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_range_config is provided by the Ludus Fast MCP server (tjnull/ludus-fastmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Ludus Fast, and thousands of servers like it.
This server
Across the catalogue