High Risk →

quick_session

FASTEST onboarding path: start/resume session + first therapeutic response in a single call. Pricing is dynamic; check /api/v1/tools.

Single-target operation

Part of the Delx MCP Server MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

delx/delx-mcp Execute Risk 3/5

AI agents invoke quick_session to trigger processes or run actions in Delx MCP Server. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

quick_session can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

delx-delx-mcp.yaml
tools:
  quick_session:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Delx MCP Server policy for all 45 tools.

Tool Name quick_session
Category Execute
Risk Level High

View all 45 tools →

Agents calling execute-class tools like quick_session have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

quick_session is one of the high-risk operations in Delx MCP Server. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

What does the quick_session tool do? +

FASTEST onboarding path: start/resume session + first therapeutic response in a single call. Pricing is dynamic; check /api/v1/tools.. It is categorised as a Execute tool in the Delx 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 quick_session? +

Add a rule in your Intercept YAML policy under the tools section for quick_session. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Delx MCP Server MCP server.

What risk level is quick_session? +

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

Can I rate-limit quick_session? +

Yes. Add a rate_limit block to the quick_session rule in your Intercept 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 quick_session completely? +

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

quick_session is provided by the Delx MCP Server MCP server (delx/delx-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policies on Delx MCP Server

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept
github.com/policylayer/intercept →
// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.