oboe_set_approval · Obo MCP: Risk & Policy

WHAT IT DOES

What oboe_set_approval does on Obo

AI agents use oboe_set_approval 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_set_approval needs a policy

The tool modifies approval status within the OBO review workflow (reversible state change on items), placing it in Write category. Severity is medium because misuse could incorrectly approve or unapprove items in a priority-tracked system, affecting review integrity, but changes are reversible.

From the tool's definition Tool name 'oboe_set_approval' combined with server context describing OBO review session management with item tracking and workflow automation. The 'set_approval' pattern indicates modification of approval state on tracked items.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

oboe_set_approval Rate-limited

oboe_set_approval 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_set_approval": {
      "limits": [
        {
          "counter": "oboe_set_approval_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_set_approval

What does the oboe_set_approval tool do? +

oboe_set_approval. 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_set_approval? +

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

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

Can I rate-limit oboe_set_approval? +

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

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

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