get_workspace_settings

THE RISK

Low Risk

Why get_workspace_settings needs a policy

This tool retrieves configuration data from a workspace without creating, modifying, deleting, or executing any operations. It is a straightforward read operation that queries existing state.

From the tool's definition Tool name 'get_workspace_settings' and description 'Get settings for a specific workspace' indicate a retrieval operation with no modification or execution of code/commands.

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

POLICY

How to control get_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 get_workspace_settings:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_workspace_settings": {}
  }
}

get_workspace_settings is read-only, so it stays allowed — but 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.

CAP 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 →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about get_workspace_settings

What does the get_workspace_settings tool do? +

Get settings for a specific workspace. It is categorised as a Read tool in the AnythingLLM MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_workspace_settings? +

Register the AnythingLLM MCP Server MCP server in PolicyLayer and add a rule for get_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 get_workspace_settings? +

get_workspace_settings is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_workspace_settings? +

Yes. Add a rate_limit block to the get_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 get_workspace_settings completely? +

Set action: deny in the PolicyLayer policy for get_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 get_workspace_settings? +

get_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 →