photogrammetry.run
Queue an evidence-bound photogrammetry lane without promoting unresolved scale.
This record as markdown: /tools/visionmcp/photogrammetry.run.md
What photogrammetry.run does on Visionmcp
AI agents invoke photogrammetry.run to trigger actions in Visionmcp. 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.
Why photogrammetry.run is rated High
This tool triggers execution of a photogrammetry processing lane, which is an external operation whose outcomes depend on provided evidence/imagery. While the operation is reversible (photogrammetry results can be discarded), it consumes computational resources and produces external side effects beyond simple data retrieval or modification.
From the tool's definition Tool description states 'Queue an evidence-bound photogrammetry lane' — 'queue' and 'run' indicate triggering an external computational operation (photogrammetry processing).
Attacks that exploit this kind of access
The rule that runs photogrammetry.run safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Visionmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For photogrammetry.run, this is the rule to start with:
photogrammetry.run 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Visionmcp, apply this rule, and every photogrammetry.run call is checked against it from then on.
Questions about photogrammetry.run
Queue an evidence-bound photogrammetry lane without promoting unresolved scale. It is categorised as a Execute tool in the Visionmcp MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Vision MCP server in PolicyLayer and add a rule for photogrammetry.run: 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 Visionmcp. Nothing to install.
photogrammetry.run 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 photogrammetry.run 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 photogrammetry.run. 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.
photogrammetry.run is provided by the Vision MCP server (joshuahickscorp/visionmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Vision, and thousands of servers like it.
Across the catalogue