chat_prompt_complete · OpenLink MCP Server for ODBC MCP

WHAT IT DOES

What chat_prompt_complete does on OpenLink MCP Server for ODBC

AI agents invoke chat_prompt_complete to trigger actions in OpenLink MCP Server for ODBC. 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 chat_prompt_complete needs a policy

The tool invokes an external OPAL backend service to process and complete a chat prompt. This constitutes executing an external operation with side effects that depend on the input arguments. It's not a simple read (it doesn't just retrieve stored data) and not a write (it doesn't create/modify structured records).

From the tool's definition 'complete chat prompt' using 'OPAL backend' — triggers an external backend operation whose effects depend on the prompt arguments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

chat_prompt_complete Rate-limited

chat_prompt_complete 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": {
    "chat_prompt_complete": {
      "limits": [
        {
          "counter": "chat_prompt_complete_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 OpenLink MCP Server for ODBC, so you can run agents against it safely.

FAQ

Questions about chat_prompt_complete

What does the chat_prompt_complete tool do? +

Tool to use the OPAL backend to complete chat prompt. It is categorised as a Execute tool in the OpenLink MCP Server for ODBC MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on chat_prompt_complete? +

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

What risk level is chat_prompt_complete? +

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

Can I rate-limit chat_prompt_complete? +

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

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

chat_prompt_complete is provided by the OpenLink MCP Server for ODBC MCP server (pvsmark/pvs-odbc-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.