Return the bounding box of the chunk's data in geographic coordinates.
AI agents call get_chunk_bounds 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.
This tool retrieves and returns existing data (bounding box/geographic coordinates) from a chunk without any side effects, modifications, or external operations. It is purely informational and matches the Read category definition of retrieval operations that have no side effects.
From the tool's definition Tool name 'get_chunk_bounds' and description 'Return the bounding box of the chunk's data in geographic coordinates' indicate a query operation that retrieves spatial metadata without modifying or executing any operations.
Documented attack patterns abuse exactly the kind of access get_chunk_bounds gives an agent:
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_chunk_bounds:
{
"version": "1",
"default": "deny",
"tools": {
"get_chunk_bounds": {}
}
}get_chunk_bounds is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return the bounding box of the chunk's data in geographic coordinates. It is categorised as a Read tool in the Metashape MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Metashape MCP Server MCP server in PolicyLayer and add a rule for get_chunk_bounds: 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.
get_chunk_bounds is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_chunk_bounds 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 get_chunk_bounds. 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.
get_chunk_bounds 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.
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.