update_cards_batch_preview · Mochi MCP Server MCP

WHAT IT DOES

What update_cards_batch_preview does on Mochi MCP Server

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

WHY IT NEEDS A POLICY

Why update_cards_batch_preview needs a policy

The tool performs updates (write operations) on multiple cards, which constitutes data modification. While it is a preview/preparatory step rather than actual application (mitigated by the two-phase commit pattern described in the server), it still represents write-class functionality.

From the tool's definition Tool name contains 'update' and description states 'Preview updates for multiple cards at once.' This is a write operation that modifies card data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_cards_batch_preview Rate-limited

update_cards_batch_preview 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": {
    "update_cards_batch_preview": {
      "limits": [
        {
          "counter": "update_cards_batch_preview_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 Mochi MCP Server, so you can run agents against it safely.

FAQ

Questions about update_cards_batch_preview

What does the update_cards_batch_preview tool do? +

Preview updates for multiple cards at once. It is categorised as a Write tool in the Mochi MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_cards_batch_preview? +

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

What risk level is update_cards_batch_preview? +

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

Can I rate-limit update_cards_batch_preview? +

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

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

update_cards_batch_preview is provided by the Mochi MCP Server MCP server (nz99/mochi-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.