Create the temporary directory used for storing index data.
AI agents use create_temp_directory to create or update resources in Code Index — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Code Index environment.
This tool creates a temporary directory, which is a reversible write operation. It does not delete, execute arbitrary code, or cause financial impact. The blast radius is minimal since temp directories are meant to be ephemeral and isolated. Confidence is high because the intent is clear from both name and description.
From the tool's definition Tool name 'create_temp_directory' and description 'Create the temporary directory used for storing index data' indicate file system creation.
Documented attack patterns abuse exactly the kind of access create_temp_directory gives an agent:
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 create_temp_directory:
{
"version": "1",
"default": "deny",
"tools": {
"create_temp_directory": {
"limits": [
{
"counter": "create_temp_directory_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_temp_directory stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create the temporary directory used for storing index data. It is categorised as a Write tool in the Code Index MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Code Index MCP server in PolicyLayer and add a rule for create_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.
create_temp_directory is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_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.
Set action: deny in the PolicyLayer policy for create_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.
create_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.
Start from Code Index, 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.
14 Code Index tools catalogued and risk-classified — across an index of 43,000+ MCP servers.