get_system_status
Get status of the RAG system including database connections
This record as markdown: /tools/aegntic-aegntic-mcp/get-system-status.md
What get_system_status does on Obsidian Elite RAG MCP Server
AI agents call get_system_status to retrieve information from Obsidian Elite RAG MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_system_status is rated Low
This tool retrieves status information about the RAG system and database connections. It performs a read-only query with no side effects, no data modification, no code execution, and no destructive actions. The blast radius of misuse is minimal—an AI agent could only obtain system health information, which does not compromise data integrity or enable harmful actions.
From the tool's definition Tool name 'get_system_status' and description 'Get status of the RAG system including database connections' indicate a query operation that retrieves system state information without modifying or executing any operations.
Attacks that exploit this kind of access
The rule that runs get_system_status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Obsidian Elite RAG MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_system_status, this is the rule to start with:
get_system_status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Obsidian Elite RAG MCP Server, apply this rule, and every get_system_status call is checked against it from then on.
Questions about get_system_status
Get status of the RAG system including database connections. It is categorised as a Read tool in the Obsidian Elite RAG MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Obsidian Elite RAG MCP Server MCP server in PolicyLayer and add a rule for get_system_status: 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 Obsidian Elite RAG MCP Server. Nothing to install.
get_system_status is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_system_status 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 get_system_status. 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.
get_system_status is provided by the Obsidian Elite RAG MCP Server MCP server (aegntic/aegntic-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Obsidian Elite RAG MCP Server, and thousands of servers like it.
This server
Across the catalogue