AI agents call capture_viewport as a supporting operation in Metashape MCP Server workflows.
Based on the name alone, 'capture_viewport' likely takes a screenshot or captures the current view in Metashape, which would be a Read operation. However, the empty description provides no confirmation. Given the context of a photogrammetry tool, it could capture the 3D viewport as an image. Classifying as Read with low confidence due to missing description.
From the tool's definition Tool name is 'capture_viewport' but description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access capture_viewport 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 capture_viewport:
{
"version": "1",
"default": "deny",
"tools": {
"capture_viewport": {
"limits": [
{
"counter": "capture_viewport_rate",
"window": "minute",
"max": 60,
"scope": "grant"
}
]
}
}
} capture_viewport gets a rate cap, and everything else on the server is denied unless you say otherwise.
Free to start. No card required.
capture_viewport. It is categorised as a Other tool in the Metashape MCP Server MCP Server, which means it performs auxiliary operations.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for capture_viewport: 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.
capture_viewport is a Other tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the capture_viewport 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 capture_viewport. 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.
capture_viewport 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.