Create a new group. Args: name: Name of the group to create Returns: Created group information
AI agents use create_group 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 a new group resource in the Ludus platform, which is a write operation that creates data reversibly. While it modifies the system state, it does not execute arbitrary code, delete data irreversibly, move money, or have destructive effects.
From the tool's definition Tool name 'create_group' and description explicitly states 'Create a new group', which is a reversible data creation operation. Returns 'Created group information' indicating it modifies state by adding a new resource.
Documented attack patterns abuse exactly the kind of access create_group 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 create_group:
{
"version": "1",
"default": "deny",
"tools": {
"create_group": {
"limits": [
{
"counter": "create_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
} create_group 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.
Create a new group. Args: name: Name of the group to create Returns: Created group information. 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 create_group: 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.
create_group 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 create_group 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 create_group. 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.
create_group 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.