Low Risk

get_point_cloud_stats

Return dense point cloud statistics.

How to control get_point_cloud_stats ↓

What get_point_cloud_stats does on Metashape MCP Server

AI agents call get_point_cloud_stats to retrieve information from Metashape MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_point_cloud_stats needs a policy

This tool retrieves and returns statistical information about a point cloud, which is a read-only operation with no side effects. It does not create, modify, delete, or execute any operations. The blast radius of misuse is minimal—an agent could only access statistics about existing data, not alter the project state or trigger external operations.

From the tool's definition The tool name 'get_point_cloud_stats' and description 'Return dense point cloud statistics' indicate a retrieval operation that queries existing data without modification, deletion, or external execution.

Documented attack patterns abuse exactly the kind of access get_point_cloud_stats gives an agent:

How to control get_point_cloud_stats

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 get_point_cloud_stats:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_point_cloud_stats": {}
  }
}

get_point_cloud_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Metashape MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_point_cloud_stats

What does the get_point_cloud_stats tool do? +

Return dense point cloud statistics. It is categorised as a Read tool in the Metashape MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_point_cloud_stats? +

Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for get_point_cloud_stats: 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.

What risk level is get_point_cloud_stats? +

get_point_cloud_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_point_cloud_stats? +

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

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

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

Enforce policy on every Metashape MCP Server tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.