Check if the Obsidian application is currently running.
AI agents call obsidian_check_app_running to retrieve information from Mcp Apple Obsidian without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves the running state of an application, which is a read-only operation that queries system state without modifying, executing code, or causing any destructive actions. The blast radius is minimal—an agent cannot misuse this to cause harm. The confidence is high because the intent is unambiguous from both the name and description.
From the tool's definition The tool name 'obsidian_check_app_running' and description 'Check if the Obsidian application is currently running' indicate a simple status query with no side effects.
Attacks that exploit this kind of access
Check if the Obsidian application is currently running. It is categorised as a Read tool in the Mcp Apple Obsidian MCP Server, which means it retrieves data without modifying state.
Register the Mcp Apple Obsidian MCP server in PolicyLayer and add a rule for obsidian_check_app_running: 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 Mcp Apple Obsidian. Nothing to install.
obsidian_check_app_running 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_check_app_running 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_check_app_running. 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_check_app_running is provided by the Mcp Apple Obsidian MCP server (rex/mcp-apple-obsidian). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →