cleanup_stale_references · CodeFlow MCP Server MCP

WHAT IT DOES

What cleanup_stale_references does on CodeFlow MCP Server

AI agents invoke cleanup_stale_references to trigger actions in CodeFlow MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why cleanup_stale_references needs a policy

cleanup_stale_references triggers real processes with real consequences. An agent gone sideways doesn't fire it once — it starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

cleanup_stale_references Rate-limited

cleanup_stale_references stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cleanup_stale_references": {
      "limits": [
        {
          "counter": "cleanup_stale_references_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about cleanup_stale_references

What does the cleanup_stale_references tool do? +

Manually trigger cleanup of stale file references in the vector store. It is categorised as a Execute tool in the CodeFlow MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on cleanup_stale_references? +

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

What risk level is cleanup_stale_references? +

cleanup_stale_references is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit cleanup_stale_references? +

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

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

cleanup_stale_references is provided by the CodeFlow MCP Server MCP server (mrorigo/code-flow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.