Cancel the currently running Metashape operation.
AI agents invoke cancel_processing to trigger actions in Metashape MCP Server. 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.
This tool interrupts/terminates an active processing operation. It's an action that triggers an external operational effect (stopping a running process), which fits Execute. While it doesn't run code directly, it controls execution state.
From the tool's definition Cancel the currently running Metashape operation
Documented attack patterns abuse exactly the kind of access cancel_processing gives an agent:
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 cancel_processing:
{
"version": "1",
"default": "deny",
"tools": {
"cancel_processing": {
"limits": [
{
"counter": "cancel_processing_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} cancel_processing 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.
Free to start. No card required.
Cancel the currently running Metashape operation. It is categorised as a Execute tool in the Metashape MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for cancel_processing: 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.
cancel_processing is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the cancel_processing 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.
Set action: deny in the PolicyLayer policy for cancel_processing. 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.
cancel_processing 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.
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.