oboe_create_child_session · Obo MCP: Risk & Policy

WHAT IT DOES

What oboe_create_child_session does on Obo

AI agents use oboe_create_child_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_create_child_session needs a policy

This tool creates a new session entity, which is a reversible write operation. It does not execute arbitrary code, delete data, or move money. The creation of a child session represents data modification within the OBO workflow system. Confidence is slightly reduced (0.75) because the tool description is empty, requiring inference from context and naming patterns.

From the tool's definition Tool name 'oboe_create_child_session' indicates creation of a new child session object within the OBO review system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oboe_create_child_session Rate-limited

oboe_create_child_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_create_child_session": {
      "limits": [
        {
          "counter": "oboe_create_child_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_create_child_session

What does the oboe_create_child_session tool do? +

oboe_create_child_session. 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_create_child_session? +

Register the Obo MCP server in PolicyLayer and add a rule for oboe_create_child_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_create_child_session? +

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

Can I rate-limit oboe_create_child_session? +

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

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

oboe_create_child_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.