Critical Risk →

network_abort_batch

Abort a running network batch.

How to control network_abort_batch ↓

What network_abort_batch does on Metashape MCP Server

AI agents call network_abort_batch to permanently remove resources in Metashape MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why network_abort_batch needs a policy

Aborting a running batch process is an irreversible action — the in-progress work is terminated and cannot be resumed from the point of interruption. This is a destructive operation with potentially high impact, as it could destroy hours of photogrammetry processing work.

From the tool's definition Abort a running network batch

Documented attack patterns abuse exactly the kind of access network_abort_batch gives an agent:

How to control network_abort_batch

PolicyLayer is an MCP gateway — it sits between your AI agents and Metashape MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for network_abort_batch:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "network_abort_batch"
  ]
}

network_abort_batch disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Metashape MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about network_abort_batch

What does the network_abort_batch tool do? +

Abort a running network batch. It is categorised as a Destructive tool in the Metashape MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on network_abort_batch? +

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

What risk level is network_abort_batch? +

network_abort_batch is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit network_abort_batch? +

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

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

network_abort_batch is provided by the Metashape MCP Server MCP server (jenkinsm13/metashape-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Metashape MCP Server tool call.

Start from Metashape MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

112 Metashape MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.