convert_batch · ContextForge MCP Gateway MCP: Risk & Policy

WHAT IT DOES

What convert_batch does on ContextForge MCP Gateway

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

WHY IT NEEDS A POLICY

Why convert_batch needs a policy

This tool creates or modifies document content through format conversion. While the operation is reversible and doesn't permanently destroy data (Destructive), it does change document state, making it a Write action. Severity is medium because batch conversion of multiple documents could affect many items, but the reversibility and lack of data loss mitigate the risk.

From the tool's definition Tool name 'convert_batch' and description 'Convert multiple documents to the same format' indicates it modifies data by transforming documents.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

convert_batch Rate-limited

convert_batch 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": {
    "convert_batch": {
      "limits": [
        {
          "counter": "convert_batch_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 ContextForge MCP Gateway, so you can run agents against it safely.

FAQ

Questions about convert_batch

What does the convert_batch tool do? +

Convert multiple documents to the same format. It is categorised as a Write tool in the ContextForge MCP Gateway MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on convert_batch? +

Register the ContextForge MCP Gateway MCP server in PolicyLayer and add a rule for convert_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 ContextForge MCP Gateway. Nothing to install.

What risk level is convert_batch? +

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

Can I rate-limit convert_batch? +

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

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

convert_batch is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.