AI agents use update_system_settings to create or update resources in AnythingLLM MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your AnythingLLM MCP Server environment.
This tool modifies system settings, which is a Write operation as it creates or modifies data reversibly. The severity is high because system settings changes can have broad impact across the AnythingLLM instance (workspace management, chat operations, document handling, user administration, AI agent configuration), affecting multiple users and workflows.
From the tool's definition Tool name 'update_system_settings' and description 'Update system settings' indicate modification of system configuration.
Documented attack patterns abuse exactly the kind of access update_system_settings gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and AnythingLLM MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for update_system_settings:
{
"version": "1",
"default": "deny",
"tools": {
"update_system_settings": {
"limits": [
{
"counter": "update_system_settings_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}update_system_settings 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.
Update system settings. It is categorised as a Write tool in the AnythingLLM MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the AnythingLLM MCP Server MCP server in PolicyLayer and add a rule for update_system_settings: 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 AnythingLLM MCP Server. Nothing to install.
update_system_settings 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_system_settings 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_system_settings. 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_system_settings is provided by the AnythingLLM MCP Server MCP server (raqueljezweb/anythingllm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from AnythingLLM MCP Server, 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.
38 AnythingLLM MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.