diagnose_vector_search · DevFlow MCP: Risk & Policy

WHAT IT DOES

What diagnose_vector_search does on DevFlow MCP

AI agents invoke diagnose_vector_search to trigger actions in DevFlow MCP. 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 diagnose_vector_search needs a policy

This tool directly queries the SQLite database, bypassing normal application abstractions. While described as a read/diagnostic operation, executing raw queries against the underlying database and circumventing security layers elevates this above a simple Read.

From the tool's definition 'Diagnostic tool to directly query SQLite database for entity embeddings, bypassing application abstractions'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

diagnose_vector_search Rate-limited

diagnose_vector_search 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": {
    "diagnose_vector_search": {
      "limits": [
        {
          "counter": "diagnose_vector_search_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 DevFlow MCP, so you can run agents against it safely.

FAQ

Questions about diagnose_vector_search

What does the diagnose_vector_search tool do? +

Diagnostic tool to directly query SQLite database for entity embeddings, bypassing application abstractions. It is categorised as a Execute tool in the DevFlow MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on diagnose_vector_search? +

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

What risk level is diagnose_vector_search? +

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

Can I rate-limit diagnose_vector_search? +

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

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

diagnose_vector_search is provided by the DevFlow MCP server (takin-profit/devflow-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.