List all markers with their coordinates and error estimates.
AI agents call list_markers 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 displays existing marker data (coordinates and error estimates) from a Metashape project without performing any side effects. It is a read-only query operation that poses minimal risk even if called inappropriately by an AI agent, as it cannot alter project state or trigger external operations.
From the tool's definition Tool name is 'list_markers' and description states 'List all markers with their coordinates and error estimates' — a pure retrieval operation with no modification, deletion, or execution of external processes.
Documented attack patterns abuse exactly the kind of access list_markers 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 list_markers:
{
"version": "1",
"default": "deny",
"tools": {
"list_markers": {}
}
}list_markers 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.
List all markers with their coordinates and error estimates. 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 list_markers: 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.
list_markers 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 list_markers 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 list_markers. 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.
list_markers 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.