index_repo · TempoGraph MCP: Risk & Policy

WHAT IT DOES

What index_repo does on TempoGraph

AI agents use index_repo to create or update resources in TempoGraph — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TempoGraph environment.

WHY IT NEEDS A POLICY

Why index_repo needs a policy

Based on the name alone, 'index_repo' most likely indexes (processes and stores) a repository into the code graph engine, which is a Write operation — it creates or modifies data (the index) in the system. Given the server context (TempoGraph, a code graph context engine), this is consistent with ingesting/embedding a repository. However, the empty description significantly lowers confidence.

From the tool's definition Tool name 'index_repo' — description is empty and uninformative.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

index_repo Rate-limited

index_repo 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.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "index_repo": {
      "limits": [
        {
          "counter": "index_repo_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches TempoGraph, so you can run agents against it safely.

FAQ

Questions about index_repo

What does the index_repo tool do? +

index_repo. It is categorised as a Write tool in the TempoGraph MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on index_repo? +

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

What risk level is index_repo? +

index_repo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit index_repo? +

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

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

index_repo is provided by the TempoGraph MCP server (tempograph). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.