pix4d_click_menu · PIX4Dmatic MCP: Risk & Policy

WHAT IT DOES

What pix4d_click_menu does on PIX4Dmatic MCP

AI agents invoke pix4d_click_menu 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_click_menu needs a policy

This tool performs GUI automation by clicking menu items in PIX4Dmatic. Clicking menus can trigger arbitrary application actions (e.g., starting processing, deleting data, exporting files, changing settings) whose effects depend on which menu path is clicked. This is an Execute-category action since it triggers external operations in the application.

From the tool's definition Click a menu or menu-like UI path by visible text labels

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

pix4d_click_menu Rate-limited

pix4d_click_menu 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_click_menu": {
      "limits": [
        {
          "counter": "pix4d_click_menu_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_click_menu

What does the pix4d_click_menu tool do? +

Click a menu or menu-like UI path by visible text labels. 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_click_menu? +

Register the PIX4Dmatic MCP server in PolicyLayer and add a rule for pix4d_click_menu: 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_click_menu? +

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

Can I rate-limit pix4d_click_menu? +

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

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

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