High Risk →

match_photos

match_photos

How to control match_photos ↓

What match_photos does on Metashape MCP Server

AI agents invoke match_photos 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.

High Risk

Why match_photos needs a policy

Based on the server context (Agisoft Metashape photogrammetry automation) and the tool name, 'match_photos' likely triggers the photo matching/feature detection process, which is a computational operation that runs processing on loaded images. This falls under Execute as it triggers an external operation. Confidence is low due to empty description.

From the tool's definition Tool name 'match_photos' on a photogrammetry server; description is empty and uninformative.

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

How to control match_photos

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 match_photos:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "match_photos": {
      "limits": [
        {
          "counter": "match_photos_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

match_photos 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.

  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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about match_photos

What does the match_photos tool do? +

match_photos. 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.

How do I enforce a policy on match_photos? +

Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for match_photos: 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 match_photos? +

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

Can I rate-limit match_photos? +

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

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

match_photos 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.