submit_review · Agent Bus MCP: Risk & Policy

WHAT IT DOES

What submit_review does on Agent Bus

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

WHY IT NEEDS A POLICY

Why submit_review needs a policy

The tool creates or updates review records that affect task workflow state (approved/rejected/changes_requested), which is reversible data modification. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read data (Read).

From the tool's definition Tool description states 'Submit verifier review for a task. Approved reviews satisfy review gates; rejected reviews mark changes_requested.' This modifies task state by updating review status and gating decisions.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_review Rate-limited

submit_review 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": {
    "submit_review": {
      "limits": [
        {
          "counter": "submit_review_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 Agent Bus, so you can run agents against it safely.

FAQ

Questions about submit_review

What does the submit_review tool do? +

Submit verifier review for a task. Approved reviews satisfy review gates; rejected reviews mark changes_requested. It is categorised as a Write tool in the Agent Bus MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_review? +

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

What risk level is submit_review? +

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

Can I rate-limit submit_review? +

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

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

submit_review is provided by the Agent Bus MCP server (mustaphasteph/agent-bus). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.