server_info

Show the current MCP server configuration: resolved project directory, database location, index status, embedding model, active config, and all currently connected databases.

ServerLocal Rag
CategoryRead

How to control server_info ↓

WHAT IT DOES

What server_info does on Local Rag

AI agents call server_info to retrieve information from Local Rag without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

THE RISK

Low Risk

Why server_info needs a policy

This tool queries and returns informational metadata about the server's current state and configuration. It has no side effects, does not modify data, execute code, delete resources, or involve financial transactions. The read-only nature and informational scope place it clearly in the Read category.

From the tool's definition Tool description explicitly states 'Show the current MCP server configuration' — a retrieval operation that displays server state, project directory, database location, index status, embedding model, active config, and connected databases.

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

POLICY

How to control server_info

PolicyLayer is an MCP gateway — it sits between your AI agents and Local Rag, and nothing reaches the server without passing your rules. This is the rule we recommend for server_info:

policy.json

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

server_info 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 Local Rag — 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 Local Rag tools

Destructive delete_annotation Remove an annotation that is no longer relevant — e.g. a bug that was fixed, a constraint Destructive remove_file Remove a specific file from the RAG index. Execute wiki Run the wiki rebuild workflow. The Write index_files Index files in a directory for semantic search. Without patterns, indexes the project from Write annotate Attach a persistent note to a file or symbol that surfaces inline in future read_relevant Write create_checkpoint Save a checkpoint so future sessions know what was done and why. REQUIRED: call this as yo Read affected Given changed files (or the working-tree diff against HEAD by default), report the test fi Read git_context Show git context for the working tree: uncommitted changes annotated with index status, re

All 29 Local Rag 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 server_info

What does the server_info tool do? +

Show the current MCP server configuration: resolved project directory, database location, index status, embedding model, active config, and all currently connected databases. It is categorised as a Read tool in the Local Rag MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server_info? +

Register the Local Rag MCP server in PolicyLayer and add a rule for server_info: 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 Local Rag. Nothing to install.

What risk level is server_info? +

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

Can I rate-limit server_info? +

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

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

server_info is provided by the Local Rag MCP server (thewinci/mimirs). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Local Rag tool call.

Start from Local Rag, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

29 Local Rag tools catalogued and risk-classified — across an index of 43,000+ MCP servers.