oboe_complete_session · Obo MCP: Risk & Policy

WHAT IT DOES

What oboe_complete_session does on Obo

AI agents use oboe_complete_session to create or update resources in Obo — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Obo environment.

WHY IT NEEDS A POLICY

Why oboe_complete_session needs a policy

This tool updates the status of a session object to 'completed', which is a write operation that changes session state. It is not destructive (the session is not deleted), not financial, and not execute (no arbitrary code/command execution).

From the tool's definition Tool description states it 'Mark[s] a session completed' — a state change operation that modifies the session record. The verb 'mark' and context of 'completed' indicate a reversible update rather than deletion or destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oboe_complete_session Rate-limited

oboe_complete_session stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "oboe_complete_session": {
      "limits": [
        {
          "counter": "oboe_complete_session_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about oboe_complete_session

What does the oboe_complete_session tool do? +

Mark a session completed when no actionable items remain. It is categorised as a Write tool in the Obo MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on oboe_complete_session? +

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

What risk level is oboe_complete_session? +

oboe_complete_session is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit oboe_complete_session? +

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

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

oboe_complete_session is provided by the Obo MCP server (warnes-innovations/oboe-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.