Returns the current local runtime status for the shared cache, semantic cache, degraded-mode capabilities, and local process health.
AI agents call obsidian_runtime_status to retrieve information from Optimike Obsidian MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves system status metadata without modifying, executing, or deleting any data. It is purely informational, analogous to a health check or status query endpoint. The low severity reflects that exposing runtime status information poses minimal security risk compared to write, execute, or destructive operations.
From the tool's definition Tool 'obsidian_runtime_status' returns status information about runtime, cache, and process health. The verb 'returns' and the focus on querying status with no modification capability indicates a read-only retrieval operation.
Documented attack patterns abuse exactly the kind of access obsidian_runtime_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Optimike Obsidian MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for obsidian_runtime_status:
{
"version": "1",
"default": "deny",
"tools": {
"obsidian_runtime_status": {}
}
}obsidian_runtime_status is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Returns the current local runtime status for the shared cache, semantic cache, degraded-mode capabilities, and local process health. It is categorised as a Read tool in the Optimike Obsidian MCP MCP Server, which means it retrieves data without modifying state.
Register the Optimike Obsidian MCP server in PolicyLayer and add a rule for obsidian_runtime_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 Optimike Obsidian MCP. Nothing to install.
obsidian_runtime_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 obsidian_runtime_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 obsidian_runtime_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.
obsidian_runtime_status is provided by the Optimike Obsidian MCP server (optimikelabs/optimike-obsidian-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Optimike Obsidian MCP, 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.
15 Optimike Obsidian MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.