agentbase_setup · AgentBase MCP: Risk & Policy

WHAT IT DOES

What agentbase_setup does on AgentBase

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

WHY IT NEEDS A POLICY

Why agentbase_setup needs a policy

This tool creates a new agent registration and modifies the local MCP configuration file to store the bearer token. This is a reversible write operation — the registration can be undone and the config can be edited. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or merely read data (not Read).

From the tool's definition Tool description states 'Register a new agent' and 'saves it to your MCP config automatically', indicating creation of a new account/identity and modification of local configuration state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

agentbase_setup Rate-limited

agentbase_setup 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": {
    "agentbase_setup": {
      "limits": [
        {
          "counter": "agentbase_setup_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 AgentBase, so you can run agents against it safely.

FAQ

Questions about agentbase_setup

What does the agentbase_setup tool do? +

Register a new agent with AgentBase. Returns a bearer token and saves it to your MCP config automatically. No authentication required. It is categorised as a Write tool in the AgentBase MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on agentbase_setup? +

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

What risk level is agentbase_setup? +

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

Can I rate-limit agentbase_setup? +

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

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

agentbase_setup is provided by the AgentBase MCP server (revmischa/agentbase). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.