generate_with_llm · Session Buddy MCP: Risk & Policy

WHAT IT DOES

What generate_with_llm does on Session Buddy

AI agents invoke generate_with_llm to trigger actions in Session Buddy. 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 generate_with_llm needs a policy

This tool triggers an external operation — calling a third-party LLM provider's API — whose effects (cost, output, external API calls) depend on the arguments passed. It doesn't merely read local data but actively executes a remote inference request. Misuse could result in unintended API calls, cost accumulation, or generation of harmful content, warranting medium severity.

From the tool's definition Generate text using specified LLM provider

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_with_llm Rate-limited

generate_with_llm 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": {
    "generate_with_llm": {
      "limits": [
        {
          "counter": "generate_with_llm_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 Session Buddy, so you can run agents against it safely.

FAQ

Questions about generate_with_llm

What does the generate_with_llm tool do? +

Generate text using specified LLM provider. It is categorised as a Execute tool in the Session Buddy MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on generate_with_llm? +

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

What risk level is generate_with_llm? +

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

Can I rate-limit generate_with_llm? +

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

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

generate_with_llm is provided by the Session Buddy MCP server (lesleslie/session-buddy). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.