pix4d_run_job_object · PIX4Dmatic MCP: Risk & Policy

WHAT IT DOES

What pix4d_run_job_object does on PIX4Dmatic MCP

AI agents invoke pix4d_run_job_object to trigger actions in PIX4Dmatic MCP. 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 IT NEEDS A POLICY

Why pix4d_run_job_object needs a policy

This tool triggers computational jobs within PIX4Dmatic that process drone imagery and generate outputs. While not immediately destructive (processing can be stopped or outputs deleted), it executes significant external operations with side effects. The 'Execute' category is most appropriate as it runs code/operations whose outcomes depend on the job parameters provided.

From the tool's definition Tool description states 'Run a job object against the current PIX4Dmatic session or an existing project_path.' The word 'run' combined with the server's stated capability to 'start processing' indicates this tool executes external operations (image…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pix4d_run_job_object Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "pix4d_run_job_object": {
      "limits": [
        {
          "counter": "pix4d_run_job_object_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches PIX4Dmatic MCP, so you can run agents against it safely.

FAQ

Questions about pix4d_run_job_object

What does the pix4d_run_job_object tool do? +

Run a job object against the current PIX4Dmatic session or an existing project_path. It is categorised as a Execute tool in the PIX4Dmatic MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on pix4d_run_job_object? +

Register the PIX4Dmatic MCP server in PolicyLayer and add a rule for pix4d_run_job_object: 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 PIX4Dmatic MCP. Nothing to install.

What risk level is pix4d_run_job_object? +

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

Can I rate-limit pix4d_run_job_object? +

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

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

pix4d_run_job_object is provided by the PIX4Dmatic MCP server (jangjo123/pix4d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.