update_workspace_settings

THE RISK

Medium Risk

Why update_workspace_settings needs a policy

The tool modifies workspace settings, which is a write operation. It does not delete data (would be Destructive), execute arbitrary code (would be Execute), nor involve financial transactions (would be Financial). Settings updates are typically reversible, making this a Write classification.

From the tool's definition Tool name 'update_workspace_settings' and description 'Update settings for a specific workspace' indicate modification of configuration data.

Documented attack patterns abuse exactly the kind of access update_workspace_settings gives an agent:

POLICY

How to control update_workspace_settings

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_workspace_settings:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_workspace_settings": {
      "limits": [
        {
          "counter": "update_workspace_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

update_workspace_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.

Create a free account and register AnythingLLM MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More AnythingLLM MCP Server tools

Destructive clear_chat_history Clear all chat history for a workspace Destructive delete_agent Delete an agent Destructive delete_api_key Delete an API key Destructive delete_document Delete a document from a workspace Destructive delete_user Delete a user Destructive delete_workspace Delete a workspace Execute initialize_anythingllm Initialize the AnythingLLM client with API credentials Execute invoke_agent Invoke an agent with input

All 38 AnythingLLM MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about update_workspace_settings

What does the update_workspace_settings tool do? +

Update settings for a specific workspace. 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.

How do I enforce a policy on update_workspace_settings? +

Register the AnythingLLM MCP Server MCP server in PolicyLayer and add a rule for update_workspace_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.

What risk level is update_workspace_settings? +

update_workspace_settings is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_workspace_settings? +

Yes. Add a rate_limit block to the update_workspace_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.

How do I block update_workspace_settings completely? +

Set action: deny in the PolicyLayer policy for update_workspace_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.

What MCP server provides update_workspace_settings? +

update_workspace_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.

Enforce policy on every AnythingLLM MCP Server tool call.

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.

CHECK YOUR STACK →