Return detailed metadata for a specific camera.
AI agents call get_camera_metadata 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 queries camera metadata information from Metashape without creating, modifying, deleting, or executing any operations. It is a passive data retrieval function with no destructive or system-altering capability. The low severity reflects minimal blast radius if misused—an agent could at worst gain visibility into camera parameters but cannot affect the photogrammetry project state or outcomes.
From the tool's definition Tool name 'get_camera_metadata' and description 'Return detailed metadata for a specific camera' indicate a read-only retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access get_camera_metadata 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_camera_metadata:
{
"version": "1",
"default": "deny",
"tools": {
"get_camera_metadata": {}
}
} get_camera_metadata 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 detailed metadata for a specific camera. 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_camera_metadata: 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_camera_metadata 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_camera_metadata 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_camera_metadata. 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_camera_metadata 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.