check_temp_directory

THE RISK

Low Risk

Why check_temp_directory needs a policy

This tool performs a read-only check/inspection of a temporary directory structure. It retrieves information about existing index data without creating, modifying, deleting, or executing anything. The use of 'check' indicates a passive inspection operation typical of Read category tools. Even though it accesses temporary storage, there are no side effects or irreversible actions possible.

From the tool's definition Tool description states it 'Check[s] the temporary directory' — a query or inspection operation with no modification or execution capability.

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

POLICY

How to control check_temp_directory

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

policy.json

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

check_temp_directory 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 Code Index — 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 Code Index tools

Destructive clear_settings Clear all settings and cached data. Execute build_deep_index Build the deep index (full symbol extraction) for the current project. This performs Execute refresh_index Manually rebuild the project file index. Use after git operations or when index seems stal Execute refresh_search_tools Manually re-detect the available command-line search tools on the system. This is usef Write configure_file_watcher configure_file_watcher Write create_temp_directory Create the temporary directory used for storing index data. Write set_project_path Set the base project path for indexing. Read find_files Find files matching glob pattern using in-memory index. Supports path patterns (.py, test_

All 14 Code Index 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_temp_directory

What does the check_temp_directory tool do? +

Check the temporary directory used for storing index data. It is categorised as a Read tool in the Code Index MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on check_temp_directory? +

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

What risk level is check_temp_directory? +

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

Can I rate-limit check_temp_directory? +

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

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

check_temp_directory is provided by the Code Index MCP server (johnhuang316/code-index-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Code Index tool call.

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

CHECK YOUR STACK →