batch · Agent Wiki MCP: Risk & Policy

WHAT IT DOES

What batch does on Agent Wiki

AI agents invoke batch to trigger actions in Agent Wiki. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why batch needs a policy

Batch execution of multiple tool calls is fundamentally an Execute operation—it triggers external operations whose effects depend on which tools are batched and their arguments. While batch itself is a wrapper, its capacity to invoke destructive, write, and financial operations (via siblings) makes it Execute rather than Write or Read.

From the tool's definition Tool name 'batch' with description 'Execute multiple tool calls in a single request' indicates it runs/triggers operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

batch Rate-limited

batch stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "batch": {
      "limits": [
        {
          "counter": "batch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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 Wiki, so you can run agents against it safely.

FAQ

Questions about batch

What does the batch tool do? +

Execute multiple tool calls in a single request. Reduces tool-call count for LLM subscriptions. It is categorised as a Execute tool in the Agent Wiki MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on batch? +

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

What risk level is batch? +

batch is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit batch? +

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

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

batch is provided by the Agent Wiki MCP server (xinhuagu/agent-wiki). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.