check_claude_code_status

THE RISK

Low Risk

Why check_claude_code_status needs a policy

This tool retrieves system state information (whether a CLI tool is installed/configured) without modifying, executing, or deleting anything. It is a simple diagnostic query with minimal blast radius if misused by an AI agent.

From the tool's definition Tool description states 'Check if Claude Code CLI is installed and configured' — a pure status check with no side effects. The verb 'check' indicates a read-only query operation.

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

POLICY

How to control check_claude_code_status

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

policy.json

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

check_claude_code_status 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 Obsidian Ai Curator — 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 Obsidian Ai Curator tools

Destructive cleanup_temp_directories Clean up temporary directories created by Claude Code Destructive git_rollback Rollback to a previous git commit Execute execute_claude_code_feature Execute Claude Code in headless mode to implement a feature Execute execute_claude_code_fix Execute Claude Code in headless mode to fix an issue Write append_to_daily_note Append content to daily note Write init_project Initialize a new project with playbook and optional repository integration Write create_bug_report Create an automated bug report from an error Write create_feature_request Create a feature request with design documentation

All 27 Obsidian Ai Curator 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 check_claude_code_status

What does the check_claude_code_status tool do? +

Check if Claude Code CLI is installed and configured. It is categorised as a Read tool in the Obsidian Ai Curator MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_claude_code_status? +

Register the Obsidian Ai Curator MCP server in PolicyLayer and add a rule for check_claude_code_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 Ai Curator. Nothing to install.

What risk level is check_claude_code_status? +

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

Can I rate-limit check_claude_code_status? +

Yes. Add a rate_limit block to the check_claude_code_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.

How do I block check_claude_code_status completely? +

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

What MCP server provides check_claude_code_status? +

check_claude_code_status is provided by the Obsidian Ai Curator MCP server (nwant/obsidian-ai-curator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Obsidian Ai Curator tool call.

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

CHECK YOUR STACK →