Share range configuration with other users. Args: target_user_ids: List of user IDs to share with make_public: Make configuration publicly accessible permissions: Permissions to grant (read, clone, modify) user_id: Optional user ID (admin only) Returns: Share result with access link
AI agents use share_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.
This tool creates or modifies access permissions and sharing configurations, which are data state changes. While it doesn't delete data or move money, it does alter who can access and potentially modify range configurations. The 'clone' and 'modify' permission options increase severity beyond a simple read-only share.
From the tool's definition Tool modifies access control and sharing settings by granting permissions to other users (read, clone, modify) and optionally making configuration publicly accessible. The action is reversible through permission revocation.
Risk signalsAdmin/system-level operation
Documented attack patterns abuse exactly the kind of access share_range_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ludus FastMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for share_range_config:
{
"version": "1",
"default": "deny",
"tools": {
"share_range_config": {
"limits": [
{
"counter": "share_range_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}share_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.
Free to start. No card required.
Share range configuration with other users. Args: target_user_ids: List of user IDs to share with make_public: Make configuration publicly accessible permissions: Permissions to grant (read, clone, modify) user_id: Optional user ID (admin only) Returns: Share result with access link. 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 share_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.
share_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 share_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 share_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.
share_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.
Deterministic rules across all 201 Ludus FastMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
201 Ludus FastMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.