camera.derive_undistorted
Derive source-linked pinhole frames while preserving pose and scale authority.
This record as markdown: /tools/visionmcp/camera.derive-undistorted.md
What camera.derive_undistorted does on Visionmcp
AI agents invoke camera.derive_undistorted 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 camera.derive_undistorted is rated High
camera.derive_undistorted triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Attacks that exploit this kind of access
The rule that runs camera.derive_undistorted 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 camera.derive_undistorted, this is the rule to start with:
camera.derive_undistorted 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 camera.derive_undistorted call is checked against it from then on.
Questions about camera.derive_undistorted
Derive source-linked pinhole frames while preserving pose and scale authority. 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 camera.derive_undistorted: 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.
camera.derive_undistorted 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 camera.derive_undistorted 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 camera.derive_undistorted. 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.
camera.derive_undistorted 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