AI agents use create_model_config to create or update resources in Mcp Llama Swap — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Llama Swap environment.
This tool creates a new model configuration file/entry, which is a reversible write operation. Given the context of model management in a Claude Code session, misconfiguration could cause service disruptions or load incorrect models, but the action itself is modifiable. Severity is medium because created configs could break the system's model-swapping functionality, though changes are reversible.
From the tool's definition Tool named 'create_model_config' on a server that manages llama.cpp model configurations. The 'create' verb indicates data creation. Description is empty, limiting certainty.
Documented attack patterns abuse exactly the kind of access create_model_config gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Mcp Llama Swap, and nothing reaches the server without passing your rules. This is the rule we recommend for create_model_config:
{
"version": "1",
"default": "deny",
"tools": {
"create_model_config": {
"limits": [
{
"counter": "create_model_config_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_model_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.
create_model_config. It is categorised as a Write tool in the Mcp Llama Swap MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Llama Swap MCP server in PolicyLayer and add a rule for create_model_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 Mcp Llama Swap. Nothing to install.
create_model_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 create_model_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 create_model_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.
create_model_config is provided by the Mcp Llama Swap MCP server (oussama-kh/mcp-llama-swap). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Mcp Llama Swap, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
4 Mcp Llama Swap tools catalogued and risk-classified — across an index of 43,000+ MCP servers.